This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-04
Channels
- # adventofcode (171)
- # beginners (160)
- # boot (13)
- # chestnut (2)
- # cider (6)
- # cljs-dev (15)
- # cljsjs (35)
- # cljsrn (1)
- # clojure (139)
- # clojure-argentina (3)
- # clojure-brasil (1)
- # clojure-greece (31)
- # clojure-italy (5)
- # clojure-russia (5)
- # clojure-spec (18)
- # clojure-uk (11)
- # clojurescript (42)
- # clojurex (6)
- # core-async (12)
- # cursive (14)
- # dirac (13)
- # emacs (13)
- # events (1)
- # fulcro (46)
- # graphql (7)
- # leiningen (10)
- # lumo (3)
- # mount (31)
- # off-topic (20)
- # onyx (30)
- # perun (4)
- # planck (47)
- # re-frame (28)
- # reagent (14)
- # ring (5)
- # shadow-cljs (3)
- # spacemacs (7)
- # specter (13)
- # timbre (3)
- # unrepl (65)
- # yada (8)
@mfikes does the env
in cljs.analyzer/analyze
contain the namespace?
nvm, figured it out. it does indeed contain the namespace.
I'm trying to get Reagent working on Node with foreign libs again, seems like https://github.com/clojure/clojurescript/commit/fc0989f1b44b97547410a2d2c807f16430b47486#diff-db201d3634488851510ee2fbce327924 broke the bootstrap script so that it only works with Node modules
the parts that affect this use case are global.require = require;
and nodeGlobalRequire
use in CLOSURE_IMPORT_SCRIPT
, other parts don't matter
Is there a way to print compiler options as they are passed to the compiler? Could be useful for debugging / tooling authors
@juhoteperi ok, that one caused way more trouble than it was worth for Node.js users
Yeah, I think I found a solution which works for both cases
Reagent is now running tests with all different environments (node/browser, npm/foreign)
Antonio thought there might be already issue about this but we couldn't find one, here's a new one with a patch: https://dev.clojure.org/jira/browse/CLJS-2430
this was just merged and probably affects CLJS interop https://github.com/google/closure-compiler/pull/2729