Fork me on GitHub
#lumo
<
2017-05-15
>
hlolli08:05:13

@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.

jonpither12:05:25

Hi. Is there a way to grab a file from the classpath, even that file could be in a jar, using Lumo?

jonpither13:05:55

Lumo is great

anmonteiro15:05:15

@hlolli I don't know what a Vinyl stream is

anmonteiro15:05:57

But to answer your question, we don't include the gulp portion of the Closure Compiler

hlolli15:05:22

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.

hlolli15:05:36

I sometimes see project where js developers are knitting togeather coffescript, jade, typescript and es6. Why not add cljs into that pipeline 馃檪

richiardiandrea15:05:38

@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?

hlolli15:05:16

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.

richiardiandrea15:05:30

Yeah the problem is , I hoped I they would adapt to the cljs wf not me adapting to the js 馃榾馃榾馃榾

richiardiandrea15:05:15

The moment I open emacs with inf-clojure people run away 馃榿馃榿

hlolli15:05:20

Think about all the people stuck with js-tooling that wish they could sneak in some .cljs code 馃槃

anmonteiro15:05:43

@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

hlolli17:05:05

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)

anmonteiro17:05:22

yeah you鈥檒l need to change that too

hlolli17:05:28

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.

hlolli17:05:45

well, I think some of the other to-js compilers also run a binary, so Im overthinking this maybe.

ag21:05:45

has anyone successfully used lumo to evaluate org-babel blocks? #emacs #org-mode

mac22:05:52

@ag No, but it sounds like a neat idea.

ag22:05:41

I wish I wasn鈥檛 so stupid and lazy. I would鈥檝e written a package. Alas I am all those things