-
Notifications
You must be signed in to change notification settings - Fork 2
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
module is not defined #6
Comments
Somehow including |
haven't figured out what is the issue with how /* eslint-disable import/no-commonjs, filenames/match-regex, import/unambiguous, global-require */
module.exports = {
webpack: {
configure: (webpackConfig) => {
webpackConfig.module.rules.push({
test: /\.(js)$/,
use: 'react-hot-loader/webpack',
include: /node_modules/,
});
return webpackConfig;
},
},
}; works. |
Thank you so much!! I've been struggling to get this working in IE 11 for awhile now and this was the ticket. All other browsers were working prior to the above, I've removed the Craco package and the webpack config code above resolved it. |
I was having this same issue and thanks @gajus your solution got me going again. I dug a bit further and found the cause of the problem. This plugin adds the bable config for react-hot-loader and the webpack alias @hot-loader/react-dom. It should just be one or the other, preferably the latter and then you don't need to use the legacy way of enabling it you just use
you can confirm this by just manually adding it to the craco.config.js, you don't even need the rest of the webpack stuff, well or this plugin I guess. Apologies @hasanayan don't mean to make it redundant, thanks for taking the time to do it in the first place.
|
@fridaystreet are you saying all you added to your craco config was the webpack alias and hot reloading works just like that? |
@riotrah yep that's right |
After adding this plugin I am getting this error:
The text was updated successfully, but these errors were encountered: