Clojurians Log v2

Hi folks, in my host page, for figwheel, should i include the /cljs-out/dev/main.js or main_bundle.js? (just started using npm import feature as well)

“Your host page will need to load the final bundled asset.” doh

nvm

Now I run into this:

[Figwheel] Successfully compiled build dev to "target/public/cljs-out/dev/main.js" in 28.101 seconds.
[Figwheel] Bundling: npx webpack --mode=development target/public/cljs-out/dev/main.js -o target/public/cljs-out/dev/main_bundle.js
[Figwheel:SEVERE] Bundling command failed
asset bundle.js 644 bytes [emitted] (name: main)

ERROR in main
Module not found: Error: Can't resolve 'target/public/cljs-out/dev/main.js' in '/Users/marten/Sites/clojure/aviationglass'

webpack 5.1.3 compiled with 1 error in 60 ms

I can confirm the file is there, as the first log line indicates.

anyone any idea?, using latest cljs and figwheel-main 0.2.11

ah, so @wcalderipe and I bumped into the same issue 🙂

https://github.com/bhauman/figwheel-main/blob/4406e9eeb312b32058398f0614a479b763dba303/src/figwheel/main.cljc#L154 Could it be that this shelling out somehow runs too early?

No that’s not it, manually running this npx command from my terminal (when main.js is definitely there), still yields this error

so, adding ./ in front would fix this

@wcalderipe $ npx webpack --mode=development ./target/public/cljs-out/dev/main.js -o target/public/cljs-out/dev/main_bundle.js does run

{:main       aviationglass.core
 :target     :bundle
 :output-to  "./target/public/cljs-out/dev/main.js" ;; the ./ at the beginning is somehow mandatory. 
 :bundle-cmd {:none ["npx" "webpack" "--mode=development" :output-to "-o" :final-output-to]}}

I figured this out by trying deliberately to run the cli command manually with a wrong filename, this yielded the exact same error. Then I just took a plunge and tried with ./ in front, and it compiled 🤷‍♂️

https://github.com/bhauman/figwheel-main/issues/266

@wcalderipe @kah0ona As was noted in your thread, try downgrading the webpack version of 4.xx. I ran into this last night and that resolves the issue. Of course, your solution of modifying the :bundle-cmd also works

haha solid timing 😉

opened an issue for it

might even be able to make a PR soon, but gtg now

and it should probably be tested through various versions of webpack i assume? not sure what the policy is on this 🙂