Lazy loading javascript assets that may no longer be available on the server
up vote
0
down vote
favorite
I am running into an issue where my older versions of my webapp (where the user hasn't refreshed the page) are lazily loading javascript assets that are no longer available. The javascript files are all tagged with like myasset.[contenthash].js
so every time I push an update there is a flurry of 404's.
Is the recommended way of dealing with this just catching the 404 and prompting the user to refresh or is there a cleaner approach?
javascript caching webpack webserver
add a comment |
up vote
0
down vote
favorite
I am running into an issue where my older versions of my webapp (where the user hasn't refreshed the page) are lazily loading javascript assets that are no longer available. The javascript files are all tagged with like myasset.[contenthash].js
so every time I push an update there is a flurry of 404's.
Is the recommended way of dealing with this just catching the 404 and prompting the user to refresh or is there a cleaner approach?
javascript caching webpack webserver
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am running into an issue where my older versions of my webapp (where the user hasn't refreshed the page) are lazily loading javascript assets that are no longer available. The javascript files are all tagged with like myasset.[contenthash].js
so every time I push an update there is a flurry of 404's.
Is the recommended way of dealing with this just catching the 404 and prompting the user to refresh or is there a cleaner approach?
javascript caching webpack webserver
I am running into an issue where my older versions of my webapp (where the user hasn't refreshed the page) are lazily loading javascript assets that are no longer available. The javascript files are all tagged with like myasset.[contenthash].js
so every time I push an update there is a flurry of 404's.
Is the recommended way of dealing with this just catching the 404 and prompting the user to refresh or is there a cleaner approach?
javascript caching webpack webserver
javascript caching webpack webserver
asked Nov 19 at 19:15
john_ryan
832823
832823
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381195%2flazy-loading-javascript-assets-that-may-no-longer-be-available-on-the-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown