This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-04
Channels
- # bangalore-clj (3)
- # beginners (23)
- # boot (89)
- # cider (11)
- # cljs-dev (22)
- # cljsjs (5)
- # cljsrn (21)
- # clojure (141)
- # clojure-android (1)
- # clojure-berlin (1)
- # clojure-greece (1)
- # clojure-italy (13)
- # clojure-mke (2)
- # clojure-nl (8)
- # clojure-norway (5)
- # clojure-russia (22)
- # clojure-sg (4)
- # clojure-spec (38)
- # clojure-uk (109)
- # clojurescript (150)
- # consulting (4)
- # core-async (7)
- # cursive (13)
- # datascript (8)
- # datomic (72)
- # dirac (185)
- # emacs (5)
- # figwheel (2)
- # flambo (1)
- # hoplon (13)
- # immutant (6)
- # lambdaisland (7)
- # lumo (46)
- # off-topic (13)
- # om (4)
- # onyx (1)
- # pedestal (1)
- # re-frame (68)
- # reagent (15)
- # rum (16)
- # slack-help (4)
- # spacemacs (22)
- # specter (3)
- # vim (10)
- # yada (28)
hrm on a first attempt Prepack fails on the generated Lumo JS
can’t really say why as their output is pretty cryptic
anyone had the idea as well of trying to use lumo to clojurescriptify? https://github.com/substack/node-browserify/wiki/list-of-transforms nothing should hinder that right?
Actually managed to get it to work
I think my phone pasted the link twice :thinking_face:
@anmonteiro that happens if you're on a spotty connection
Not much because all it matters is the snapshot in the end
But there might be runtime perf gains to be had
@anmonteiro sure, but hoping to apply it to other projects. Good to have number ideas roughly for them. 😛
@jonpither is anything not straightforward in the API?
I’m always looking for feedback
Is it documented? It was odd I couldnt call it inside the lumo repl, but could from inside a cljs ns. I guess this is a known semantic?
really?
that sounds weird
I can definitely (require '[lumo.classpath :as cp])
@jonpither not documented yet, sorry, working on it
you can always (dir lumo.classpath)
and use doc
at the REPL
I don’t know how to do that
I’ve only ever succeeded at installing the latest
what’s your problem?
For the SDK change in Cursive, I’d like to try the --version flag in a version that didn’t support it (1.2.0, AFAICT) so that I can detect that error message and warn the user they need to upgrade.
other than that the error will be the same as if you do lumo --askjbfkuasj
Thinking about it, even if that bug is fixed in 1.2.0, I’d be making that check for one single version (1.2.0) so perhaps it’s not worth it.
are you actually working on adding Lumo support to Cursive now? 🙂
Since previous versions have the infinite loop. I guess I’m going to have to deal with that anyway.
I was just continuing some investigations, but it’s a bit of a yak shave right now. I’m trying to build my latest version and I use a lumo script there now, and working on the script in Cursive without support is a PITA so I got sidetracked 🙂
hopefully a good rabbit hole to go down to 🙂