Thomas Heller

The key is passed as bind here? https://github.com/thheller/shadow-cljs/blob/051b5ecc7d701ef45b3bbc839685ac6ea03d4ad7/src/main/shadow/cljs/devtools/server/nrepl.clj#L138 I'm using `:host` since it is more consistent with all the other options in shadow-cljs which also use `:host`. Is that causing...

Printing EDN currently caps out of 1mb to avoid printing forever. The UI just doens't handle the error correctly yet. There probably should be a way to increase the cap...

Cannot comment without more information. `:shadow` should handle all features `:closure` handles just fine since it is using the same closure compiler do the the code transformations.

Ah, `babel` gets a bit over-eager. It rewrites the code to require the `regeneratorRuntime` which is their way of rewriting generators and then requiring a library to actually run it....

I'm not going to add anything regarding the regenerator-runtime to shadow-cljs directly. I'd instead make the above change the default so it isn't required in the first place. Polyfills themselves...

This isn't at all related to what expo thinks of as `.expo.js` files. This just happens to be a `shadow.expo` CLJS namespace being compiled to `shadow.expo.js`. This is a regular...

Sorry, I don't use Nix and don't have the slightest clue what would be involved in creating a package. I also don't know what you'd gain by doing so. `shadow-cljs`...

Can you be more precice in what shadow needs to do here? Can't you just set `"manifest_version": 3` in the JSON file? shadow really doesn't care whats in your manifest....

Well, it is read-**eval**-print-loop. So no, you can't have a REPL without eval.

No. Why would it be?