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

webpack-hot-middleware/client reload params configured to true #72

Merged
merged 1 commit into from
Mar 23, 2016

Conversation

Boychenko
Copy link
Contributor

I think it will be better DX to have full reload when webpack gets stuck.config
This very useful for case when HMR fails due to stateless functional components. It's easy to reproduce for top level components like App or AboutPage

@coryhouse coryhouse merged commit 2a7a2fe into coryhouse:master Mar 23, 2016
@coryhouse
Copy link
Owner

Great call! Didn't even know this option existed. My only hesitation is some people will be confused by how sometimes a full reload occurs. I believe the rule is top-level components will always require a reload. Are there other instances this would occur? Regardless, I agree this is a win, so merging. Thanks for the PR!

@Boychenko
Copy link
Contributor Author

I didn't find description about reload conditions. Documentation doesn't say something concrete. It says that reload happens when webpack stucks. Also this option was mention in breaking changes on version 2.0.0.

@Boychenko Boychenko deleted the webpack-hot-middleware-reload branch March 23, 2016 03:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants