This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-01
Channels
- # announcements (3)
- # babashka (17)
- # beginners (163)
- # bristol-clojurians (1)
- # calva (18)
- # chlorine-clover (17)
- # clj-kondo (13)
- # cljs-dev (50)
- # cljsjs (3)
- # cljsrn (13)
- # clojure (218)
- # clojure-dev (5)
- # clojure-europe (9)
- # clojure-italy (10)
- # clojure-nl (8)
- # clojure-uk (107)
- # clojurescript (25)
- # conjure (163)
- # cursive (63)
- # data-science (9)
- # datomic (38)
- # docker (1)
- # figwheel (34)
- # figwheel-main (3)
- # fulcro (15)
- # graalvm (1)
- # helix (12)
- # jobs (3)
- # juxt (5)
- # kaocha (3)
- # lein-figwheel (2)
- # leiningen (6)
- # luminus (2)
- # malli (1)
- # meander (12)
- # nrepl (4)
- # rdf (2)
- # re-frame (2)
- # reagent (7)
- # reitit (5)
- # remote-jobs (2)
- # rum (1)
- # shadow-cljs (65)
- # spacemacs (27)
- # tools-deps (18)
- # vim (19)
- # xtdb (2)
I haven't heard much since last weekend's release issues, anything I missed that should go into a bugfix release?
haven’t had the chance to play with the :bundle
target in depth yet, but to respond to the above re: the guide, I think that tekacs was reading the guide step by step and didn’t understand the state they were in would be remedied by executing the next step.
I am puzzled why :bundle
creates a main.js or the cljs http server serves a main.js if one isn’t there, let alone why it appears to be in such a broken state (it contains clearly invalid JS)
might not be worth fixing atm, since the happy path does work once we figured it out
@lilactown :bundle
doesn't create anything itself, it respects :output-to
like all other targets
maybe pointing to the specific part of the guide where this happens would shed some light
the user setup a cljs build with target :bundle
, but did not try to bundle it in any way with a JS bundler yet
😄 if you see no issue here, then I’ll drop it. I think the user had an expectation to follow the guide step by step and when they got into a broken state, instead of continuing they tried to understand the broken state.
serving a broken main.js
if one isn’t on disk seems weird, but if you see no issue then I won’t pursue further
@lilactown there's just lack information in nearly everything that has been said so far 🙂
So — if you don’t run the bundler, it serves a main.js even if there’s not one on disk
Broken in the way I outlined in the original thread — it has incorrectly generated JS syntax in it
I appreciate that you’re told to run the bundler first, but if (like me) you’re trying to adapt the tutorial for another bundler and it fails to generate main.js, you’re going to be fairly confused when the server ‘correctly’ serves a main.js when there’s none on disk... only one that’s broken
browser REPL generates a main.js
if none found so you can use the browser REPL anywhere you want
If it weren’t broken then you could continue without feeling that something is blocking
for sure, thanks for bringing up again @lilactown and being patient with my confusion about what was going on