Skip to content
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

Hot Module Reload not working after upgrade to webpacker 3.0 #724

Closed
krisrang opened this issue Aug 31, 2017 · 5 comments
Closed

Hot Module Reload not working after upgrade to webpacker 3.0 #724

krisrang opened this issue Aug 31, 2017 · 5 comments

Comments

@krisrang
Copy link

Hot Module Reload does not seem to be working correctly after upgrading to webpacker 3.0.
The page is receiving the HMR update and page content is changing but then a full refresh is also done.

@gauravtiwari
Copy link
Member

gauravtiwari commented Aug 31, 2017

@krisrang Oh yes, seems like something we introduced with watchContentBase but apparently we seem to have manifest.json in there that will change and it will make the page refresh:

To fix now:

// config/webpack/development.js
const environment = require('./environment')
const config = environment.toWebpackConfig()
config.devServer.watchContentBase = false
module.exports = config

@gauravtiwari
Copy link
Member

Merged the fix but Keeping this open for reference until we make a new tiny release

renatodeleao added a commit to renatodeleao/webpacker-rails-example that referenced this issue Sep 1, 2017
@gauravtiwari
Copy link
Member

Released 3.0.1

@eidge
Copy link

eidge commented Dec 14, 2017

Still seeing this, using webpack 3.0.1 and webpack 3.4.1

Tried @gauravtiwari fix, but no success either.

Any ideas?

@coorasse
Copy link

I wrote a detailed explanation on how to use hot module reloading with Webpacker, that could help you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants