Would it be helpful to create a spec for the shadow cls config? I could see that along with Bruce's spell spec lib going a long way to catching some configuration mistakes up front.

they are already partially spec'd

Great, I'll take a look and see if I can do anything more.

https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/build/config.clj and then each target extends the multispec https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/build/targets/browser.clj

could probably do more though but I don't like closing down the config format too much. so to some degree I don't it want to complain about keys it doesn't know

maybe only if they are somewhat close to some known keys

dunno how the spell check stuff does stuff

question for the compiler nerds here: what is the correct term for this in compiler terms? https://ask.clojure.org/index.php/8879/cljs-should-macros-support-lifting-vars-to-the-ns-level

Any idea how I can resolve this problem?

The required JS dependency "@babel/runtime/helpers/interopRequireDefault" is not available, it was required by "node_modules/react-dates/lib/index.js".

Search in:
	/Users/user/my-project/node_modules
You probably need to run:
  npm install @babel/runtime/helpers/interopRequireDefault

npm install @babel/runtime/helpers/interopRequireDefault
npm ERR! code ENOLOCAL
npm ERR! Could not install from "@babel/runtime/helpers/interopRequireDefault" as it does not contain a package.json file.

I've trying to import the react-dates npm package

I would like to use shadow-cljs to require arbitrary npm and cljs dependencies from a self hosted clojurescript repl. I saw example at https://github.com/thheller/shadow-cljs/blob/0e28c615cd75d4cbce27ede7a8f7f70785d42c86/src/dev/demo/selfhost/simple.cljs. Now my question is to allow dependency definition at runtime - do I have to start shadow cljs via command line with generated settings files. Or would I rather run it via its compiler api?

What I want to do is provide dependencies for a few important cljs and npm dependencies out of the box. And then everything else should be fetched from npm / maven at runtime and be served to the load-fn in the browser repl.

Is there any reason to be using deps.edn aliasing to leverage shadow-cljs?

I use deps.edn for local libraries

@grounded_sage likely a dependency conflict of @babel/runtime. ie. react-dates depending on a different version than present in node_modules/@babel/runtime

@hoertlehner the self-hosted stuff only supports "pre-packaging" npm dependencies. if you want to do it dynamically then you must build that yourself using regular self-hosted cljs stuff. shadow-cljs can't help for those.

@thheller I'd like to know how I can fix this. But in the meantime I am using HTML date input element because I'm just prototyping atm.

make sure all the right versions are installed. standard dependency conflict resolving.

@thheller Thanks Thomas! Could you point me to the location where you do the npm prepackaging in your code?

I can but none of that will be relevant to the self-hosted stuff. It uses the Closure Compiler heavily which is written in Java and won't be available for self-hosted

https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/build/targets/bootstrap.clj

this does all the packaging but its mostly using standard shadow-cljs stuff

how do you check for dependencies update?