This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-15
Channels
- # beginners (34)
- # boot (45)
- # cider (16)
- # cljs-dev (20)
- # cljsjs (1)
- # cljsrn (8)
- # clojure (207)
- # clojure-berlin (3)
- # clojure-dev (18)
- # clojure-greece (1)
- # clojure-ireland (1)
- # clojure-italy (9)
- # clojure-russia (20)
- # clojure-spec (27)
- # clojure-uk (19)
- # clojurescript (110)
- # code-reviews (2)
- # cursive (7)
- # data-science (2)
- # datomic (7)
- # devcards (1)
- # emacs (4)
- # graphql (1)
- # hoplon (2)
- # immutant (15)
- # jobs (5)
- # jobs-rus (1)
- # juxt (1)
- # luminus (7)
- # lumo (26)
- # microservices (3)
- # off-topic (27)
- # om (13)
- # onyx (11)
- # pedestal (7)
- # proton (4)
- # re-frame (24)
- # remote-jobs (1)
- # spacemacs (2)
- # specter (2)
- # unrepl (31)
- # untangled (7)
- # vim (14)
@anmonteiro did you make an attempt to implement https://github.com/google/closure-compiler-js/blob/master/lib/gulp.js so that a lumo build could return a vinyl stream? Was thinking to make a go at this problem if the case is not.
Hi. Is there a way to grab a file from the classpath, even that file could be in a jar, using Lumo?
@jonpither see https://github.com/anmonteiro/lumo/blob/master/src/cljs/bundled/lumo/io.cljs
Indeed
@hlolli I don't know what a Vinyl stream is
But to answer your question, we don't include the gulp portion of the Closure Compiler
Ok, so I give this experiment a try, if successful I will make a pull request and we can make adjustments. The goal I have in mind, is to call the lumo build.api from a gulpfile, this would enable developing cljs parallel to js, or simply use js build/dev tools on .cljs files.
I sometimes see project where js developers are knitting togeather coffescript, jade, typescript and es6. Why not add cljs into that pipeline 馃檪
@hlolli curious because I am facing some issue in pushing a repl-oriented workflow to js devs. Is it more idiomatic to use the compile and reload wf or a Repl for that in your experience?
well, the js devs always have the browser console, I think a modern js-dev uses something like gulp to hot-reload code changes, seperating vendor from assets and sending assets into stream, enables quite fast hot-reload, like we are use to from Figwheel. I don't see adding a cljs-build-api to js-land would encourage repl-oriented workflow as far as I see, but lumo can always be started to load the files. One has to find it's best practicies I guess.
Yeah the problem is , I hoped I they would adapt to the cljs wf not me adapting to the js 馃榾馃榾馃榾
The moment I open emacs with inf-clojure
people run away 馃榿馃榿
Think about all the people stuck with js-tooling that wish they could sneak in some .cljs code 馃槃
@hlolli right so it could be as simple as changing the entry point here: https://github.com/anmonteiro/lumo/blob/master/scripts/bundleForeign.js#L7
I will give it a try, but I was earlier today seeing if changing this here https://github.com/anmonteiro/lumo/blob/master/src/cljs/bundled/lumo/closure.cljs#L290 where adding a get function for require('google-closure-compiler-js').gulp(); in lumo.js (and add that to lumo globals)
yeah you鈥檒l need to change that too
not sure if this will work at all, need to see if it is possible to write to a stream pipeline if I run the lumo binary from a node child process. I hack around and see what I get.
well, I think some of the other to-js compilers also run a binary, so Im overthinking this maybe.