-
Notifications
You must be signed in to change notification settings - Fork 137
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
SPA: Lazy loading / code splitting components & code changes #176
Comments
I run into this issue a lot Uncaught Error: Loading chunk # failed Seems it can be caused by two issues.
I think an option to keep the X previous build would be great. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature request
I'm using code splitting / lazy loading of components that are partly split based on which page you are at. However if I deploy a new version all the hashes changes and the old files are gone using this module. So then changing page just gives a 404 error when it requests that's page js.
https://webpack.js.org/guides/code-splitting/
I have tried webpack standard splitting:
And
loadable/component
But the
import
command itself doesn't seem to be try-catchable, even when done it still breaks the page.What is the expected behavior?
Some way to keep old files for a defined time.
What is motivation or use case for adding/changing the behavior?
Sites not being broken during new deployments
How should this be implemented in your opinion?
Allow an option to only delete files after x amount of days. So it can for example only delete files that haven't changed for 30 days.
For now I have to stop using this plugin :'(
The text was updated successfully, but these errors were encountered: