Clojurians
#cljs-dev
<
2017-05-14
>

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

thheller12:05:17

> I just wrote a thing for all the node / webpack folks out there, looking for any kind of feedback. https://groups.google.com/forum/?fromgroups=#!topic/clojurescript/AGXku7Ous0Y

roman01la14:05:50

@thheller not sure, but this seems to be even more confusing, especially for newcomers :thinking_face:

roman01la14:05:32

I mean, it doesn't seem to be useful except an interesting experiment. Maybe you could describe a use case where devs coming from JS would want to use this?

thheller14:05:58

@roman01la well it assumes that you know npm and then you just get cljs. no complicated cljs configs, no :externs. it just works

thheller14:05:24

imagine that was no lein dependency, the preview just uses it

thheller15:05:09

@roman01la maybe this makes the intent a little clearer

dnolen16:05:04

@thheller like I said, analyzing cljs.core twice isn’t intentional - I can’t offer any insight into why that’s happening right now

dnolen16:05:31

it maybe that we analyze it and then we also compile it - which isn’t intentional

dnolen16:05:57

since core is precompiled

thheller16:05:14

@dnolen yeah I solved that by moving the check. still works normally but won't complain about cljs.core.