Clojurians
#cljs-dev
<
2018-06-18
>

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

kommen08:06:35

@mfikes anything I might be able to help with for https://dev.clojure.org/jira/browse/CLJS-2757?

kommen08:06:44

@juhoteperi nope, thanks for the pointer, will try

kommen08:06:28

still reproduces for me with latest master

kommen08:06:18

or not… after cleaning, I get a different error

mfikes12:06:44

I’ve added some other projects to Canary (`re-frame`, om, specter, etc.) https://github.com/cljs-oss/canary

mfikes12:06:38

(These are clones of the upstream projects, set up for Canary, here https://github.com/chkup)

juhoteperi12:06:04

@mfikes No CircleCI example yet?

dnolen13:06:31

@kommen the module error is very suspicious, sounds like some Node.js thing made it through

dnolen13:06:42

have you tried to load the dep directly?

dnolen13:06:13

that is, a minimal case showing that the specific dep is problematic

dnolen13:06:20

and not the surrounding stuff

kommen13:06:09

@dnolen I tested with this minimal example https://github.com/kommen/cljs-slate as well as the repl example mike provided in https://dev.clojure.org/jira/browse/CLJS-2757

dnolen13:06:56

@kommen but I mean did you try w/o slate?

dnolen13:06:11

i.e. only the problematic dep

bhauman18:06:06

the new cli has been so immensely helpful for duplicating errors and trying things out :rocket:

dnolen18:06:47

@kommen is this actually a regression?

dnolen18:06:11

or perhaps @mfikes you know? Just curious if it ever worked

mfikes18:06:11

@dnolen I don't know if it is actually a regression or if transitive NPM deps have ever worked.

dnolen18:06:55

well I mean we know transitive deps work in general

dnolen18:06:11

React itself has tons of deps

mfikes18:06:41

Yeah, I have another project that involves transitive NPM deps, and it works.