Clojurians
#lumo
<
2017-02-08
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

shaunlebron16:02:28

@stbgz: I started experimenting to see what a good cljs tool might look like on Node

shaunlebron16:02:42

for the parts that are not possible in Node yet, I shell out to Java

shaunlebron16:02:11

just to focus on the UX, so we can replace the parts with Node as they came

shaunlebron16:02:40

Lumo happened, so I put that in. your dep resolver isn’t fully compatible yet, so I had to leave it out for now

shaunlebron16:02:40

the worst part about leaving the jvm is not having figwheel

shaunlebron16:02:57

project is ~300 lines of cljs/clj, all the hard work is done elsewhere

stbgz16:02:41

@shaunlebron that’s great I am on the same boat.. like @anmonteiro said we should definitely pool our efforts it seems there are a few us trying to build something similar

stbgz16:02:33

I spent some time looking at cljs.closure I think our challenge is going to be transforming that file to a cljc file

stbgz16:02:52

using the google-closure-compiler-js