3 ms·
Yep. But having this feature only in shadow-cljs doesn't do much for the ecosystem as a whole since non-portable. With this change, many tools, cljsbuild, Figwh
by swannodette 6y ago
Yep. But having this feature only in shadow-cljs doesn't do much for the ecosystem as a whole since non-portable. With this change, many tools, cljsbuild, Figwheel, etc. have the same capabilities. It also opens the door for creating ClojureScript libraries that depend on node_modules and these can again be consumed with any tool.
- tekacs 6y agoThank you so much for all of your work on ClojureScript, @swannodette! I love the work that's been done on shadow-cljs (and the maintainer is amazing) -- I've had a vastly easier and more stable time than with JS bundlers. That said, in building a business on top of Clojure(Script), it's incredibly reassuring to know that shadow isn't a single point of failure. This feature will make integrating/selling ClojureScript into existing projects easier too -- I only wish that I'd had this when moving from company to company a few years ago -- I'd have brought ClojureScript to a number of places. :)
- yomly 6y ago@swannodette In the library case does the cljs built library need a clojure runtime bundled? Or does banning eval and running it through Closure allow for only the bare minimum to be pulled through?
- dkersten 6y agoThanks David, that sounds pretty great!
- christophilus 6y agoJust wanted to pile on the thanks, too. CLJS spoiled me for just about any other way of doing front end work.