This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-06
Channels
- # adventofcode (99)
- # announcements (9)
- # aws (3)
- # babashka (22)
- # beginners (90)
- # boot (2)
- # calva (22)
- # cider (8)
- # clj-kondo (14)
- # cljsrn (20)
- # clojure (24)
- # clojure-europe (4)
- # clojure-italy (3)
- # clojure-losangeles (1)
- # clojure-nl (83)
- # clojure-spain (1)
- # clojure-spec (46)
- # clojure-uk (43)
- # clojuredesign-podcast (70)
- # clojurescript (40)
- # cursive (25)
- # datomic (9)
- # duct (3)
- # emacs (14)
- # figwheel-main (2)
- # fulcro (61)
- # graalvm (8)
- # juxt (7)
- # kaocha (2)
- # leiningen (19)
- # luminus (5)
- # malli (58)
- # off-topic (4)
- # re-frame (11)
- # reitit (5)
- # rewrite-clj (3)
- # shadow-cljs (63)
- # sql (5)
- # testing (5)
- # tools-deps (26)
- # uncomplicate (2)
- # vim (4)
@deas btw I looked a bit over the CLJS sources yesterday and I'm fairly certain that your "conditional" require is not supposed to work and only works accidentally 😛
once you get to know the JS npm ecosystem up close and personal it'll definitely become your favorite ... thing to avoid ... :face_vomiting:
Remember Google closure maintainers struggling with node modules years ago. That still the case?
I really hope they get their act together with this ESM stuff ... thus mess needs to end
if you mean running random node_modules code through :advanced
then yes that will never happen
Wonder how many really popular but messy node modules are out there. I mean, I would assume that React and others along those lines are pretty strict and clean by now.
I wish ... quite the opposite actually. they also don't ship ESM at all. only precompiled stuff.
Hello, why https://github.com/day8/re-frame/blob/master/docs/CodeWalkthrough.md out of the box displays "Not found. Missing index.html." in the browser? Is there any bug reported on this or do I miss some dependencies?
the example tells you to open example.html
? which url did you load? there is no index.html
?
Hey @thheller, I don't want to clog up https://github.com/thheller/shadow-cljs/issues/611 with possibly off topic stufff so I figured I would move my questions here
So I removed the :rewrite-polyfills
like you suggested but am still encountering the same error
Running a completely fresh recompile, cleaned out .shadow-cljs
and my output folder (not that it is needed) I get....
Uncaught TypeError: $jscomp.initSymbol is not a function
at okta-sign-in.entry.js:14983...
Compiled with cli version: 2.8.80 node: v12.3.1
and running on server cli version: 2.8.80 node: v12.3.1
just to confirm
i've had far less problems with npm recently than before -- but am using both (depending very much on the project)
I prefer npm because that generally leaves me closer to what most users are using
but yarn has two things that help a lot: running any script as yarn scriptname
and resolution to pin arbitrary packages
on a side note, i think one of the values of yarn was (is?) that it may have "motivated" improvements on npm's side :)
@UG1C3AD5Z That is in fact what I was wondering: Did yarn
get npm
to do things properly and can we all get back to using the default thing.
npm did improve a lot since yarn came along
at the moment it's almost a matter of preference
@UJVKWJTGE I'd say pinning matters a lot. I don't want to get different results every other day - when not changing code myself that is
if you want to publish things you should still go with npm, because npm is the real registry
the thing that prevents you from getting different versions is the lockfile
both have a lockfile: yarn.lock
and package-lock.json
they have slightly different philosophies but both ensure subsequent installs where your direct deps don't change won't get different dep trees
when I mentioned resolutions, it's a different feature
oh no, that's even slightly safer than yarn.lock
package-lock contains more information than yarn.lock
the thing I like about resolutions
is that it lets you control transitive dep versions, which is very useful when they inadvertently break
We have tons of deps everywhere. For the project we are working on, I'd aim at maximum defense wrt to dependencies getting out of control.
Been using maven for ages, but still learnt a ton about many details that haven bitten me just recently.
@royalaid I can't reproduce your error. I can require @okta/okta-signin-widget
just fine and it loads just find in dev and release builds. maybe you can try setting :compiler-options {:output-feature-set :es6}
although it works without for me
@thheller my super janky repro so far hasn't triggered the issue so I am going to spend some more time trying to figure specifically why this is happening