This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-31
Channels
- # announcements (1)
- # beginners (171)
- # cider (51)
- # clj-kondo (40)
- # cljsrn (5)
- # clojure (68)
- # clojure-dev (42)
- # clojure-europe (2)
- # clojure-italy (20)
- # clojure-spec (2)
- # clojure-uk (141)
- # clojurescript (19)
- # community-development (4)
- # core-async (17)
- # core-logic (3)
- # cursive (11)
- # data-science (1)
- # datomic (7)
- # defnpodcast (2)
- # figwheel (9)
- # figwheel-main (2)
- # fulcro (15)
- # graphql (21)
- # jackdaw (3)
- # joker (11)
- # juxt (1)
- # luminus (12)
- # off-topic (2)
- # pathom (73)
- # pedestal (2)
- # re-frame (41)
- # reagent (14)
- # reitit (4)
- # shadow-cljs (39)
- # tools-deps (4)
Is there a way to download a project's dependencies without compiling with shadow-cljs? For context, I'm working on a build dockerfile, and I'd like to download dependencies before copying the source directory in for caching purposes.
Also, I'm using deps.edn to write my dependencies.
Realized I could create a separate, dummy build and compile that without copying in the full source directory, using that compile to download dependencies. Should be a good enough workaround.
@codonnell if you use deps.edn
anyways just call clj
directly, eg clj -Stree
or so
I’m so mad at the npm world right now. Bumping react-bootstrap from 1.0.0-beta9 to 1.0.0-beta10 just opens a huge can of worms.
Does shadow-cljs have parity with webpack on how it resolves node modules? I can’t imagine that people in JS land go through this all the time, but perhaps I’m wrong and they do.
Well, I’m not sure I understand entirely — things fail to load because some js error. The latest is from Vega.js complaining about "renegeratorRuntime" is undefined
.
I rolled back my update because I have more important things to do and things work again.
renegeratorRuntime
is some babel thing for transpiled code that needs to be included separately for some reason
Another one was _uncontrollable.default is undefined
which probably relates to the uncontrollable
package. What’s the root issue? Who knows.
Yeah I tried putting nested dependencies at the top. I’ve also tried yarn, not sure if that was a good idea.
should be getting better with webpack5 since they are dropping a bunch of those ugly hacks
now webpack just accepts all sorts of crap and as long as it works in webpack people don't pay attention if things are actually correct or not
Thanks. I tried that and found that a bunch more dependencies were downloaded when I compiled. In the cold light of morning it's now obvious that the reason for that is I didn't call clojure
with the dev alias.
Does shadow pick up “nested” node_modules dependencies? (not sure what the right terminology is). Like, node_modules/react-overlays/node_modules/uncontrollable
— when there is a top-level node_modules/uncontrollable
as well?
Ah, that’s why I’m having trouble then. There’s version conflicts and apparently that works fine in the npm world.
well it works fine in that you'll have 2 uncontrollable
packages included in your build 😉
Yeah, and of course uncontrollable
released a version 7.0 who’s only change is to break the default exports. Now all the consumers have to change, and of course not everyone has done yet.
but yeah stuff like that is gonna get way worse for a while when webpack 5 is released