IMHO the webpack ecosystem and CLJS can live happily side by side, why is it important that they know about each other? Good JS interop ensures that both sides can interact well.
What would you expect from a loader that you'd be willing to give up the Closure Compiler? On Thursday, May 11, 2017 at 6:45:02 AM UTC+2, Jiyin Yiyong wrote: > Already an old boring topic... I'm from JavaScript side and so many people > are building apps with Webpack. And so many of alt-js languages got Webpack > loaders: > > BuckleScript https://github.com/rrdelaney/bs-loader > PureScript https://github.com/ethul/purs-loader > Elm https://github.com/elm-community/elm-webpack-loader > Fable https://github.com/fable-compiler/Fable > > Exception: > > No Webpack for ReasonML > https://github.com/chenglou/reason-react-example/blob/master/webpack.config.js > > Can we make a loader for ClojureScript? > > Or how about the possibility? I guess Closure Compiler will get in the why. > But is it possible if I don't use dead code elimination from Closure > Compiler? I know many people need it but seriously no other solutions? And > how much does ClojureScript depend on Closure Library? -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at https://groups.google.com/group/clojurescript.
