Thomas Heller

Would it be enough if this only worked in `release` builds? I assume in development you have control over the web server?

`2.8.81` lets you set `:compiler-options {:source-map-suffix ".foo"}` which defaults to `".map"` for `release` builds.

To put this into more context that doesn't have to be reconstructed from slack history: shadow-cljs currently uses a bundled [semver.js](https://github.com/npm/node-semver) file via the graal-js ScriptEngine to eliminate possible conflicts...

In `2.18.0` I have removed support for the `semver` checks entirely and just use the first `deps.cljs` `:npm-deps` version specified for each package. This is the simplest solution that allows...

Good catch. That used to be part of the `:browser` build process checking the installed version but ended up more noise than actual usable info. I removed it a while...

@pepe I have seen it but it is not relevant. It is just a wrapper for the API (which you can use if you want) but it doesn't do anything...

I just pushed a pretty significant rewrite of the internals for this and the config now works differently. Given this `manifest.edn` ```clojure {:name "Getting Started Example" :version "1.0" :description "Build...

Oops, another thing I added is the support for `:init-fn demo.chrome.bg/init`. This function will be called when your module is loaded. If you don't want that you can use the...

Yeah the first iteration co-located the config entries within the chrome config but was limiting in some ways. Now it could be moved since its just the `:shadow/outputs` key. Could...

`2.3.31` will automatically re-configure (and compile) the build when the `manifest.edn` config file is changed. The build config now also supports setting `:manifest-file` which should be a path to a...