This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-06
Channels
- # aleph (2)
- # arachne (4)
- # aws (3)
- # beginners (196)
- # cider (131)
- # cljs-dev (208)
- # clojure (193)
- # clojure-boston (1)
- # clojure-dev (26)
- # clojure-greece (4)
- # clojure-italy (26)
- # clojure-losangeles (1)
- # clojure-russia (11)
- # clojure-spec (40)
- # clojure-uk (78)
- # clojurescript (168)
- # cursive (25)
- # datascript (1)
- # datomic (31)
- # docker (8)
- # docs (1)
- # emacs (20)
- # fulcro (62)
- # hoplon (3)
- # jobs (1)
- # leiningen (3)
- # luminus (1)
- # nrepl (25)
- # off-topic (10)
- # other-languages (3)
- # parinfer (11)
- # planck (37)
- # portkey (54)
- # protorepl (11)
- # re-frame (2)
- # reagent (19)
- # remote-jobs (1)
- # ring (2)
- # rum (8)
- # shadow-cljs (23)
- # spacemacs (4)
- # uncomplicate (6)
- # unrepl (77)
- # vim (56)
- # yada (2)
@lilactown you can set it in ~/.shadow-cljs/config.edn
. that config will be merged with the one in the project
@hlolli thats a bug in shadow-cljs. just forgot to include the binding for REPL code. fixed in [email protected]
I’ve just set up one additional module in my project, and am trying to understand the :module-move
warnings (dozens of them now appear). The source says ;; only warn when a file is moved to a module it wouldn't be in naturally
would you expect these warnings if, eg. following the guide, one creates an empty :shared
module in order to collect common dependencies? then there would be no deps in :shared
at all ‘naturally’
hmm, after upgrading from shadow 2.1.4
to 2.2.4
, I am getting a Cannot call a class as a function
error at runtime:
shadow$provide.module$node_modules$graphql$language$source = function(g, v, m, r, l) {
Object.defineProperty(l, "__esModule", {
value: !0
});
l.Source = void 0;
m("module$node_modules$graphql$jsutils$invariant");
l.Source = function(a, f, c) {
throw new TypeError("Cannot call a class as a function");
}
}
;
@mhuebert this is due to the newer closure compiler version. it was fixed recently but not released yet. https://github.com/google/closure-compiler/issues/2822
you can downgrade the closure compiler manually by adding [com.google.javascript/closure-compiler-unshaded "v20180101"]
to your deps
you can "fix" it by just declaring the namespaces that get moved as :entries
for :shared
there should be a better diagnostic than :module-move
but thats what we have for now
only warning it should print if an actual entry you specified gets moved because that might actually be a problem