Thomas Heller

Yes, for dev builds the "ESM" is a bit hacked together. So that REPL and hot-reload still work. release builds looks entirely different. Are you saying that `release` also doesn't...

I'm more interested in hearing what you are doing, that leads you to this message in the first place? I don't see that message often and in all cases and...

Why `ctrl+c` in the first place?

How is `target/scssbuild` accessible via web? `:watch-dir` only allows one option since it assumes there is only one http root. It doesn't need to watch anything else since it is...

Only solution I can offer for now is outputting to `resources/public/css` and gitignoring that. Saves a bunch of config as well.

I can reproduce the problem when using `load-file` and your "flat" namespaces. I can also reproduce moving the namespaces to a proper structure (ie. no single-segment namespaces, `util` becomes `my.util`)...

In a `:npm-module` build shadow-cljs will not be processing or providing any npm dependencies. That is left to the tool that runs everything, so probably node/storybook? I don't know why...

This problem can also be re-produced with a xterm.js (version 5.0.0). ``` npm install [email protected] google-closure-compiler npx google-closure-compiler --js node_modules/xterm/lib/xterm.js ``` Results in ``` node_modules/xterm/lib/xterm.js:1:4095: Originally at: node_modules/xterm/lib/webpack://xterm/./src/browser/AccessibilityManager.ts:172:6: ERROR -...

FWIW I sort of built my own testing setup bypassing the built-in Cursive support entirely. Its just a tiny helper namespace and 2 custom REPL commands. The first command is...

Note that `package.json` is completely irrelevant when it comes to resolving stuff. `shadow-cljs` never looks at it for the regular project. Only the contents of the `node_modules` folder are considered...