@tekacs I can repro your issue on my laptop too

Thank you for that, @lilactown. Since Helix is yours, I wonder if you might know why using a basic Helix entrypoint in core.cljs (in that exact repro repo) causes Helix to fail to compile, too: https://gist.github.com/tekacs/a46476615782a45f29005d15bc0f27b7

how are you building the main.js bundle using parcel?

I’m not — didn’t get that far

yeah, I replied in a thread underneath your original message

Ah, sorry for not noticing

I don't think helix's master branch will work without shadow-cljs atm

going to try and fix that this weekend

Thanks very much 🙏

I think that you must generate the main.js yourself

in the webpack guide, webpack consumes out/index.js and generates out/main.js

which begs the question: WTF is the out/main.js that the CLJS http server is serving?

Hmm — I took out/main.js from the CLJS splash screen that came up on a build with no index.html

I think that it’s generated on the fly by the REPL option to cljs.main

Which is why you can’t just use the compilation output

To see it for yourself, delete index.html

And go to localhost:9000

yeah

If anyone has an example using parcel I would love to see it

I'll hopefully have one for you @dpsutton once I get this working 🙂

I'm trying to setup the :bundle-cmd now, I think that will fix this

Would love to see it. I looked over the parcel docs and couldn’t find where you put the config file. And my experiments kept failing with not finding goog

I have a bunch of shadow projects -- last week it took me two days to go from an empty directory to a fairly large, working project -- so I'll probably write that setup up soon. That said, I'd love to get this setup to be comfortable too and to maintain making it easy for people to get started with this stuff for a while -- because for all folks' complaints about CLJS tooling, I've had an infinitely easier time of it (with shadow, admittedly) than I had with a great deal of JS bundling (even CRA!).

ugh, the parcel docs are for parcel@1 :face_with_rolling_eyes:

haha I'll quickly build it using parcel and see if that helps -- just give me a sec

these are Parcel 2 docs by the way, @lilactown: https://parcel2-docs.now.sh/

I can confirm that properly generating the main.js using parcel fixes the issue above

that makes sense @lilactown -- I'll push ahead on that approach then and see how it goes 🙂

thanks for looking into it!

https://github.com/Lokeh/cljs-issue-reproduction-1

I wonder what is being served as the default file there by CLJS... 😅

had it served nothing I would have thought it was wrong immediately, but I assumed that it was safe to use the file that hadn't been pre-processed -- it's unclear why a broken main.js exists there -- perhaps it's left over from another build target but is in a broken state on the :bundle one?

@lilactown is that parcel 1 or 2? (heard yall talking about doc version)

I downgraded to parcel 1 since those were the docs i found.

👍

the only thing I didn't immediately see when glancing through parcel 2 docs was how to change the output file

did you see that in parcel 1 docs? i couldn't find any config file

I just used CLI args

there were just snippets that applied but didn't know where it should go

Parcel is all about having no config file AIUI, @dpsutton

https://parcel2-docs.now.sh/getting-started/configuration/

ahh. well there's my confusion 🙂

thanks both of you

bundle-cmd {:none ["npx" "parcel" "build" "out/index.js" "--out-dir" "out" "--out-file" "main.js" "--no-minify"]

to set the output path you can use package.json

the only thing I couldn't figure out was how to pass the NODE_ENV through the bundle-cmd

{"main": "out/main.js"} in package.json will set the output path 🙂

so it's using prod versions of React 😕

80            (for [a (range 10) b (range 10)]
              ^--- Wrong number of args (3) passed to: cljs.core/for
81              [:div a]
82              [:div b]
83              )

I have the following code:

(deftest test-async

  (let [result (waitFor (+ 1 2))
        ;; landing (<p! (waitFor
        ;;       #(see/landing!)
        ;;       ))
        ;; click (<p! (waitFor
        ;;       ;;#(see/landing!)
        ;;       #(interact/click-login-btn)
        ;;       ))
        
        ]
    (async done
           (go
             (is (= 3 (<p! result)))
             (prn "done")
             (done)
             )
           
           )
    
    ))

Is it possible to produce a source map that isn't written relatively to the output-dir, but also isn't included in sourceMapURL? I am uploading the sourcemap to a service which processes them. I see now why this is a problem :)

what is the best way to achieve the kind of routing implemented by react-router where when you click a link on any page, the browser does not perform a reload? I was thinking a potential way of doing this is creating a reagent component that encapsulates a HTML <a> tag that receives click events but calls (. e preventDefault) on them. Does anyone here have thoughts on this?