-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
HMR clears the component state #6308
Comments
Any thoughts or comments on this? Does it work for anybody else? Does it behave in same way in React version? |
@mtuzinskiy This may have been fixed by #6094. Can you test using |
@jonrimmer That would be great! I tried to update the
|
@mtuzinskiy can you try clearing your node_modules and possibly your yarn.lock? |
@shilman Yes that was it. But unfortunately it didn't solve the problem. I created the sample project, which uses |
@shilman Can we please reopen it?.. |
Yes it's still a bug |
@jonrimmer could you have a look at this repro? |
AFAIK, this seems to still be an issue, at least for me with a React application using the latest packages. |
Yes, CodeSandbox does this safely, but Storybook doesn't (as of 5.3.9) |
Please provide a reproduction for Storybook 7. I will close this. Feel free to reopen it, if it is still not working. |
I use Angular Storybook. When I change something slightly (i.e. the component's SCSS), the input fields of my simple component get cleared, and the whole state is lost.
To Reproduce
Steps to reproduce the behavior:
1.
config
is among the [HMR] updates:Expected behavior
The state of inputs should persist. That's what the HMR for, not just for live reloading.
System:
The text was updated successfully, but these errors were encountered: