This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-28
Channels
- # aws (5)
- # aws-lambda (1)
- # beginners (133)
- # boot (1)
- # cljsrn (1)
- # clojure (28)
- # clojure-austin (3)
- # clojure-italy (2)
- # clojure-spec (17)
- # clojure-uk (18)
- # clojurescript (38)
- # cursive (6)
- # datomic (6)
- # figwheel (1)
- # graphql (1)
- # klipse (1)
- # leiningen (1)
- # off-topic (13)
- # onyx (30)
- # re-frame (44)
- # reagent (7)
- # shadow-cljs (77)
- # spacemacs (7)
how does shadow-cljs deal with local maven packages? While boot picks it up ok, shadow-cljs complains it cannot find the package in maven
not really, I took cljsjs.fabric from the official repo, and modified it, then run boot package
to install it to local maven
or a plugin of some kind? I’m using https://github.com/cemerick/pomegranate which I think boot uses too?
yeah I restarted the process... I'm using cljsjs.fabric
because there are some issues with using it directly from npm (can't find jsdom
)
fixed in [email protected]
please report all packages that fail to import properly, that actually revealed two issues. the important one is fixed 😉
https://code.thheller.com/blog/shadow-cljs/2017/09/15/js-dependencies-going-forward.html
the issue is that some npm packages “disable” certain requires via “browser” overrides in package.json
btw, you mentioned shadow.cljs.devtools.api
... how can I use it from a boot script? It's cljs, right?
I’m really do not know much about boot in a clojure REPL you’d just (require 'shadow.cljs.devtools.api) (shadow.cljs.devtools.api/compile :foo)
I suppose boot can do that somehow, I never understand how there task system works exactly
I do not know anything about boot .. does boot install
when you release something or not?
I'm getting Uncaught ReferenceError: process is not defined
when trying to load the js
just need to know which package is causing the issue, shadow-cljs release app --source-maps
should help track it down
@dimovich [email protected]
should fix the process
issue and make it easier to track problems by printing the name of the thing that failed to execute in the console
(function() {
if (typeof document !== 'undefined' && typeof window !== 'undefined') {
return;
}
meaning that everything that follows will not be executed … but that doesn’t quite work since my bundler doesn’t understand the if
I can fix it so it doesn’t error out but it will still include the http dependency although it shouldnt
[email protected]
now behaves like webpack
would … 34kb overhead until the above issue is fixed