Thanks, that worked. The change specifically had to be made in the :build configuration rather than the top level:
{:source-paths ["src/dev" "src/main" "src/test"]
:dependencies [[reagent/reagent "2.0.0-alpha2"]
[cljs-http "0.1.49"]]
:dev-http {8080 {:root "public" :proxy-url "http://localhost:5000" :proxy-predicate rgrr.server/proxy?}}
:builds {:client {:target :browser
:js-options {:export-conditions ["module" "import" "browser" "require" "default"]}
:modules {:main {:init-fn rgrr.client.app/init}}}}}
I don’t plan on building a large complex application, so hopefully I won’t run into the scenario you’ve described. If I understand the problem correctly, there are still many packages that are shipped as CJS, and shadow-cljs prefers CJS. I wonder if there’s a way to make this issue more apparent? I would never have figured this out on my own.
On an unrelated note, :proxy-predicate is not mentioned in the :shadow-cljs user guide at Shadow CLJS User’s Guide This was necessary for working with a non-clojure backend server. I could not work out where the documentation source resides, otherwise I would have contributed a PR.