This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-12
Channels
- # adventofcode (112)
- # architecture (1)
- # beginners (55)
- # boot (26)
- # cider (19)
- # cljs-dev (19)
- # cljsjs (1)
- # cljsrn (7)
- # clojure (140)
- # clojure-android (3)
- # clojure-austin (3)
- # clojure-china (3)
- # clojure-gamedev (1)
- # clojure-greece (43)
- # clojure-spec (75)
- # clojure-sweden (5)
- # clojure-uk (21)
- # clojurescript (66)
- # core-async (2)
- # core-logic (1)
- # cursive (63)
- # datascript (5)
- # datomic (4)
- # devcards (2)
- # duct (13)
- # editors (5)
- # emacs (9)
- # figwheel (4)
- # fulcro (42)
- # graphql (25)
- # immutant (7)
- # jobs (29)
- # leiningen (13)
- # lumo (7)
- # numerical-computing (3)
- # off-topic (22)
- # om (2)
- # onyx (25)
- # pedestal (3)
- # re-frame (14)
- # reagent (20)
- # remote-jobs (1)
- # ring-swagger (3)
- # rum (12)
- # shadow-cljs (9)
- # uncomplicate (1)
- # unrepl (6)
Hello, I’ve run into an issue when trying to use a native NPM module (date-fns) with CLJS 1.9.946. I’ve tried to set up a simple repo (https://github.com/dkozma/npm-issue) that tries to reproduce this using just a base lein figwheel template. Essentially, when I run lein figwheel
initially, everything works, however if I quit out of the process, then run lein figwheel
again, I get an error saying Undefined nameToPath for date_fns
, and I have to lein clean
before running lein figwheel
again for it to work. Is this a known issue or should I submit this to the CLJS issue queue?
you should try to reproduce the problem without Figwheel if you want to report something
@dnolen Here is the test case using mies as a base: https://github.com/dkozma/npm-issue-min
@koz Recommend filing an issue in JIRA without using any downstream tooling or links to repos. See https://clojurescript.org/community/reporting-issues
Phew, I think I finally got JS Module information out of new Closure, it required reflection to create one class but maybe I can find another way now that I got this working (@anmonteiro)
@koz as @mfikes said, reporting ClojureScript issues means no tooling but ClojureScript itself
OK, I’ve never imported NPM modules without using any tooling whatsoever so I’ll have to look into how to make a reproducible test case doing that and will create an issue if I succeed
@dnolen Added https://dev.clojure.org/jira/browse/CLJS-2440 - unfortunately I messed up on the title and don’t seem to have any edit permissions, so I put the correct title as a comment.
@koz What Node/npm versions you you have?