You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may actually be a bug in webpack. When using webpack in watch-mode or in the dev-server (which uses watch-mode) if a file is written to, webpack compiles, and written to again, the second webpack compilation will include the the version from the first compilation of that file. Best signs from hard-source shows that modules are correctly invalidated. But it may be some other bit from hard-source causing the module to still use the old info.
This is highly unlikely to affect users though considering the the circumstances required.
The text was updated successfully, but these errors were encountered:
This may actually be a bug in webpack. When using webpack in watch-mode or in the dev-server (which uses watch-mode) if a file is written to, webpack compiles, and written to again, the second webpack compilation will include the the version from the first compilation of that file. Best signs from hard-source shows that modules are correctly invalidated. But it may be some other bit from hard-source causing the module to still use the old info.
This is highly unlikely to affect users though considering the the circumstances required.
The text was updated successfully, but these errors were encountered: