Thomas Heller

Your cider setup appears to be incorrect? This should have never worked regardless of version? The last screenshot showing the `ClojureScript REPL init form` is what you'd be using for...

Try adding `:js-options {:babel-preset-config {:targets {:chrome 50}}` or so to your build config.

The amplify libraries nowadays make heavy use of webpack specific features that shadow-cljs does not support. You may need to use webpack as described [here](https://code.thheller.com/blog/shadow-cljs/2020/05/08/how-about-webpack-now.html#option-2-js-provider-external) to get those working.

Did you run `webpack` AFTER shadow-cljs has finished compiling? It generates the `target/index.js` so you need to run `webpack` every time this file may have changed. The only time it...

And you are loading the generated `webpack` output before loading the CLJS output? (ie. `script` tags in the correct order and not `async`) Also the error message implies that you...

This is not so much a problem with webpack. shadow-cljs will have the same issues. The JS/npm world is transitioning from commonjs to ESM which means what they export may...

I really cannot answer without a reproducible example. With or without webpack, just need something to actually look at.

Thanks for the repro. As expected `webpack` does indeed default to using the `"module"` build, which means that the old commonjs style `const vegaEmbed = require("vega-embed")` becomes `import vegaEmbed from...

Changing the require on `oz` side will break everything still using the CommonJS variant (eg. default `shadow-cljs`). Definitely can't do that yet. I guess `oz` could add a check on...

You can use `deps.edn` or `project.clj`. `shadow-cljs.edn` itself does not support git dependencies.