seeing a $jscomp
polyfill error again. Wondering if there’s anything I should keep for a reproduction before I nuke .shadow-cljs/
to make the error go away?
hmm yeah I don't know how that happens
somehow somewhere the polyfill information is lost
does is not go away if you restart the watch?
sorry for the late reply, doesn’t go away if I force compile or restart the watch
concretely it’s $jscomp.asyncExecutePromiseGeneratorFunction is not a function
I have the feeling this happens on our project every time we change the package.json
I've been having $jscomp
issues as well, I removed .shadow-cljs/
and $jscomp
is back in the release build, thanks for the tip @mkvlr