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, 20
On Thursday, May 11, 2017 at 6:08:30 PM UTC+8, Thomas Heller wrote:
> 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 tha
On Wednesday, May 10, 2017 at 11:45:02 PM UTC-5, 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
> Pur
It would be nice if we can require ClojureScript in JavaScript, and let
Webpack to handle so many issues.
For Webpack use cases, I tried to sell ClojureScript to other front-end
developers around me, but saw some problems:
* IMPORTANT: hard to install JVM. For JavaScript projects, installing
Node
I'm way too biased towards the Closure Compiler and giving that up is simply
not an option for me. I am however very interested in making things simpler for
everyone.
https://github.com/thheller/shadow-devtools/wiki/ClojureScript-for-node.js-libraries
This is an example of how I intend to do th
I wrote some things down here:
https://github.com/thheller/shadow-devtools/wiki/ClojureScript-for-the-browser#productionrelease-builds
Code splitting is done by the :modules, whether or not you want to use the
loader is up to you. I personally don't but that is because I have a rather
traditiona
On Friday, May 12, 2017 at 1:55:24 AM UTC-7, Thomas Heller wrote:
> I'm way too biased towards the Closure Compiler and giving that up is simply
> not an option for me. I am however very interested in making things simpler
> for everyone.
>
> https://github.com/thheller/shadow-devtools/wiki/Cloj
Time not enough to read every detail, but I found it great that most of my
points are covered in the Wiki, code splitting, file hashing, async loading.
However I think it's not we current have for all ClojureScript users, since
it's implemented by yourself based on lein, like hashing
https://githu
> However I think it's not we current have for all ClojureScript users, since
> it's implemented by yourself based on lein
That is incorrect. It is a pure Clojure library with no dependency on
leiningen. I just happen to use leiningen and do not know enough about boot to
create proper instruct
Cool Hope one day it's in Lumo too XD
On Sat, May 13, 2017 at 1:48 AM Thomas Heller wrote:
>
> > However I think it's not we current have for all ClojureScript users,
> since it's implemented by yourself based on lein
>
> That is incorrect. It is a pure Clojure library with no dependency on
On Saturday, May 13, 2017 at 3:47:01 AM UTC+2, Jiyin Yiyong wrote:
> Cool Hope one day it's in Lumo too XD
Not by me but the features could certainly be ported.
I spent quite a bit of time yesterday fighting through webpack sources trying
to come up with an efficient way of doing things.
Th
> I'll probably write the simple version today and see how things work out.
So the simple version sort of works.
http://thheller.com/webpack-cljs-preview/index.html
http://thheller.com/webpack-cljs-preview/bundle.js
This was generated by "webpack -d" and
index.js:
---
var foo = require("webpack
I started a new topic [1] for the implementation.
You can find an example here:
https://github.com/thheller/npm-module-example
I'd be very interested in feedback from people that actually use webpack
already.
[1] https://groups.google.com/forum/?fromgroups#!topic/clojurescript/AGXku7Ous0Y
--
13 matches
Mail list logo
