lumo 2018-05-30

I have no idea how native node modules work

but yeah it would probably break down there

so for now the deps + deploy on server probably is going to be: git pull, yarn install and for running, just lumo + some options

btw, I would assume native modules would also break the single js file deploy

The nice thing about wasm, is that you can convert the binary to a base64 and bundle it in single js file. But yeh, no way with native modules.

is anyone using cljs-ajax on node perhaps?

tried promesa, but their alet macro is not supported in self-hosted cljs

@borkdude I am on a quest to post stuff to self-host, promesa is on my list but it is a difficult horse to tame

I used got for now

(.then (got WEATHER_API #js {:json true})
       #(let [body (js->clj (.-body %)
                            :keywordize-keys true)]
          ...))

nice!

does anyone see the problem here?:

ip-192-168-100-202:scripts jonathan$ lumo -sfKq --classpath `pwd`:/Users/jonathan/.m2/repository/clj-time/clj-time/0.14.2/clj-time-0.14.2.jar -A error
cljs.user=> 
cljs.user=> (require '[clj-time.core :as t])
No such namespace: clj-time.core, could not locate clj_time/core.cljs, clj_time/core.cljc, or JavaScript source providing "clj-time.core"

@johanatan I am not sure that lib is self-host compatible

it's the canonical example on the deps.edn announcement on http://clojure.org

or moment, which is a fine js lib

Typically Clojure does not work in self-host ootb - first problem is the namespace, should be .cljs, second problem is if there are macros involved

having fun 😄

yeah, could probably make snake or tetris with this 😉

@borkdude this probably won't work with native node modules. But I'm also not sure what your use case is, just throwing it out there.