Fork me on GitHub
#shadow-cljs
<
2017-10-22
>
mhuebert08:10:48

@thheller hah good timing, someone in #re-frame today was trying to get re-frame-trace to work with shadow-cljs. I posted an explanation of what we figured out yesterday: https://clojurians.slack.com/archives/C073DKH9P/p1508662534000031 feel free to correct/suggest alternatives

mhuebert12:10:01

:failed-to-compare "github:braintripping/Keypress#4477249" "github:braintripping/Keypress#4477249" #error {
 :cause "TypeError: Invalid SemVer Range: github:braintripping/Keypress#4477249"

thheller14:10:16

@mhuebert one thing I noticed in the re-frame thing :closure-defines {re-frame.trace.trace-enabled? true}

thheller14:10:30

but day8.re-frame.trace.preload

thheller14:10:40

is the define missing a day8.?

thheller14:10:06

hmm looking at the code no such goog-define exists?

thheller14:10:52

ah nvm its not part of re-frame-trace

richiardiandrea17:10:36

@thheller i don't thing you've seen it, but in lumo we were thinking about deploying Cljs to npm and how to put info in package.json. I think we are on the brink of needing it anyways šŸ˜„

thheller18:10:59

@richiardiandrea not sure I understand the intent here. why would we ā€œneedā€ it?

thheller18:10:18

at this point I see more harm than benefit in that

richiardiandrea18:10:41

How do you load clj in shadow-cljs now? From maven?

richiardiandrea19:10:46

So that would allow to consume them from npm

richiardiandrea19:10:30

So companies don't have to have two mirrors, one for maven, one for npm

richiardiandrea19:10:40

If they work with ClojureScript

thheller20:10:03

I donā€™t see that changing anytime soon

thheller20:10:34

not really sure that it should either

thheller20:10:57

problem with introducing a new package manager is that you will end up having packages that are only available in one

thheller20:10:31

so someone using only lumo will publish their package to npm naturally

thheller20:10:00

and then someone from the JVM side canā€™t consume it

thheller20:10:40

we are already in a weird situation overall with JS packages

thheller20:10:51

cljsjs vs npm and so on

thheller20:10:56

having CLJS packages declaring :npm-deps is already complicated, the reverse would make it even more complicated

richiardiandrea20:10:36

Gotcha, yeah, it will go the way you described anyways, because it is not feasible to do both, so Clojure package maintainers will eventually choose. Our tooling did not make the choice that other *Script languages have taken (use npm) so we carry this burden with us now.

thheller20:10:33

Iā€™m not sure which problem you are trying to solve still

thheller20:10:07

publish to npm is not a problem per se, as long as you keep JVM semantics (ie. classpath and namespaces)

thheller20:10:39

if you just want to allow require("some-cljs-thing/foo/bar") where that resolves to bar.cljs thats a problem

thheller20:10:15

anyways .. its good to explore alternatives ā€¦ so just do it and see where it goes

thheller20:10:22

would help to have a formal description of the goal and decisions made