New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't build with cross-env - Error: spawn webpack ENOENT #9
Comments
That's weird. I noticed the HMR issue and added the For now we need to set the production env variable to avoid including HMR and also to increase the thread pool to overcome a If anybody can help with the Windows support it would be very welcome! |
@NogsMPLS played a lot with this kind of issues, maybe he can help! |
Hey @ktmn I noticed this issue was created 4 days ago. This is right around the time that I had a PR get merged into the cross-env repo. However, I don't know if you If possible, could you pull/fetch the latest from this repo and then It should work, as the whole reason I put in the PR to cross-env was because I was getting ENOENT issues before as well. SIDE NOTE: the current react-toolbox-example repo has npm scripts run against |
Great! @ktmn can you try it? |
My bad I completely forgot to post here, but I resolved the issue by reinstalling react-toolbox. So basically, yes, what Nogs said. And now I understand why it actually worked. Thanks! |
Great! |
I faced a similar issue and the fix was to make sure the fields of the |
Cloned repo, ran install, ran start - works fine. Ran build - get this error:
So I tried to set node env manually
But it didn't work or something, because the built react-toolbox.js file will still look for __webpack_hmr EventSource, so hmr appears to be still enabled.
The problem also appears in my actual project, that I used react-toolbox in. I eliminated any trace of hmr from my source files yet it still kept showing up - turns out it was from the source of react-toolbox. So how do I let it know that the "node env" is "production"?
Also tried to do it in the webpack.config.file.js file
Nothing changed.
The text was updated successfully, but these errors were encountered: