Closed rberger closed 4 years ago
Please try 2.10.9
. I think that should fix it.
You may want to look into :ns-aliases
for the re-frame-tracing stuff so you can get rid of the :dev/:prod
aliases. See https://github.com/day8/re-frame-debux#option-2-namespace-aliases-with-shadow-cljs
Just to formally say that moving to the more recent version did fix the issue if you want to close this
I am adding this here because this issue is what pops up first when googling the error:
Check if you have a shadow-cljs version mismatch between package.json and your deps.edn/project.clj dependencies. That was it for me. Happy coding!
We have a somewhat complex webapp using AWS Amplify and Appsync. All was working fine with shadow-cljs 2.8.110.
When I noticed we were running with such an old version, I upgraded to 2.10.8 which worked fine in dev mode locally.
But the application stopped working when we did the release with the error in the chrome debugger (the following was from a run that was built with
shadow-cljs -A:prod release app --debug
):Not sure if its related but the release builds would give warnings:
All of those are defined in imported javascript files:
The first one is local to the repo in
src/aws-exports.js
The other three are in a dependency repo/jar (omnypay/visx-schema).Warnings 1 and 2 are not relavent, but the others only show up with shadow-cljs 2.9.7 onward and it seems to not work with 2.9.7 onward. 2.9.6 and earlier would not give these errors and the ones I sampled would function correctly without errors.
The other strange thing is with 2.9.7 page wouldn't load at all. Unfortunately I didn't record the error. It was a one liner about missing a parenthesis.
2.9.8 would fail with:
My shadow-cljs.edn is:
deps.edn:
Any suggestions? Thanks