This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-15
Channels
- # aws (1)
- # beginners (6)
- # boot (25)
- # cider (30)
- # cljs-dev (50)
- # cljsrn (45)
- # clojure (98)
- # clojure-austin (5)
- # clojure-czech (1)
- # clojure-dev (21)
- # clojure-dusseldorf (29)
- # clojure-germany (2)
- # clojure-greece (117)
- # clojure-italy (2)
- # clojure-nl (4)
- # clojure-russia (26)
- # clojure-serbia (10)
- # clojure-spec (123)
- # clojure-turkiye (1)
- # clojure-uk (27)
- # clojured (13)
- # clojurescript (57)
- # core-async (18)
- # cursive (13)
- # datomic (20)
- # defnpodcast (16)
- # emacs (8)
- # events (2)
- # figwheel (3)
- # instaparse (1)
- # jobs (3)
- # jobs-discuss (39)
- # klipse (9)
- # lumo (100)
- # mount (1)
- # numerical-computing (1)
- # off-topic (22)
- # om (34)
- # onyx (17)
- # pedestal (1)
- # perun (29)
- # re-frame (60)
- # reagent (16)
- # remote-jobs (8)
- # rethinkdb (6)
- # ring-swagger (19)
- # rum (1)
- # slack-help (1)
- # specter (3)
- # untangled (1)
- # yada (17)
Is it a known issue that compiler fails to find a namespace when using a dependency with a single source file core.clj
(no *.cljs files) ?
it works only with :require-macros
having the same namespace in cljs
also solves this
@roman01la what you’re saying is not very clear
I’ll post a repro later here
does it mean that :require-macros
explicitly tells compiler to look for clj
files, but with other forms of require
compiler first requires cljs
?
when users :require
foo.cljs
, we will automatically bring in the macros since they have the same namespace
that’s good to know, thanks! 🙂
^ just merged
I attached a patch to http://dev.clojure.org/jira/browse/CLJS-1935, but can't set the patch field.
Crossing my fingers that this upstream JavaScriptCore issue might be garnering traction / interest, given the recent slew of comments https://bugs.webkit.org/show_bug.cgi?id=139847
I'm looking at the google closure compiler changelog and I see that there is an unreleased change that adds a --module_resolution
flag with a NODE
option that uses the node module resolution algorithm. Would this be something that would replace the need for cljs.build.api/node-inputs
and its corresponding npm dependencies?
@chris-andrews it’s not related
ok, thanks
the module situation is kind of confusing right now
ok, so something along the lines of cljs.build.api/node-inputs
will need to stick around to handle that
thanks for the explanation
@dnolen thanks for that link, the context is really helpful
@dnolen are you familiar with cljs.pprint
‘s code?
this macroexpand
call doesn’t let self-hosted load cljs.pprint
https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/pprint.clj#L84
I think that’s about the only thing preventing cljs.pprint
from being loaded by bootstrap
the error we get now is form is not ISeqable at line 84 cljs/pprint.clj
I can’t figure out why it would throw that error, so I thought I’d share and ask for help 🙂
ah I thought macroexpand
would work in that case
right
I’ll try that approach, thanks