Closed krisquigley closed 7 years ago
With a quick look react-dom-server
is an invalid dependency and might cause a conflict.
Edit!
Alternatively the way the loader currently handles react-dom/server
is wrong as the tmp filenames seem odd with stuff like /node_modules/react-dom/dist/react-dom.min.js/server
Thanks, I added it as part of debugging for this error. I've removed it now and original issue still stands.
Is there anything I can do to help debug this?
This might be of use https://github.com/facebook/react/issues/8788 I am also assuming that /node_modules/react-dom/dist/react-dom.min.js/server
or at least the min.js
part is being called as this is being compiled for production.
Does this help? https://github.com/xjamundx/webpack2-example/issues/1
So in short, add alias for react-dom/server
so that it results in /node_modules/react-dom/dist/react-dom-server.min.js
which is the filename it should be if I recall it correctly.
Closing after two months of silence.
This issue is still happening right now on Next.js 2
In development, It works really fine. But it can't build with the same error.
I try to fix it by configure webpack's config with this
config.resolve.alias = {
'react-dom/server': path.resolve('./node_modules/react-dom/dist/react-dom-server.min.js'),
};
It can build but after built. It throw this error.
Any help?
I'm really loving react-lazy, thanks a lot for a great library! Unfortunately, I can't get it to work in production...
When running
yarn build
I get the following error on heroku and locally:package.json
Webpack