That's true.
Maybe not CommonJS but a version of JS compatible with LTS Node. That way you can develop with ClojureJS also on the Back End.
Maybe not CommonJS but a version of JS compatible with LTS Node. That way you can develop with ClojureJS also on the Back End.
You can `import` and `export` just like in the browser (and in TypeScript) as long as your files come with the `.mjs` extension. Cherry adds this extension by default, so I imagine it comes with the server in mind.
You can also keep the `.js` extension and configure this behavior in the `package.json` to run the same files both client- and serverside.
Some libraries still expect to run as CommonJS, but then you might find an "es" version if you poke around in their repositories.