Replies: 11 comments 14 replies
-
|
Hi @dimaip our CDN doesn't behave like that and we purge the cache for your projects with each new deployment and this is typically what most users want at the end of the day. What you can do is have your service worker handle fetching assets and if a 404 is encountered due to a missing asset, you can update the service worker with the new assets. Here's an article that might be of help to you: https://deanhume.com/displaying-a-new-version-available-progressive-web-app/ |
Beta Was this translation helpful? Give feedback.
-
|
For over a year I've been looking to do code splitting with Vercel, however given that this issue still remains, it's impossible for is to go that route. From a UX perspective we wouldn't want our users bothered with notifications of new app versions, as our app is stateful and performing the needed refresh would result in users losing their form edits or their progress in a video (being a video platform). From our point of view, the only reasonable solution would be to have the option of retaining older deployment versions. I don't know if there's an optimal retention period where you'd be certain that users would've migrated over on their own, but at least having a few hours of old asset retention on the CDN would be ideal. Is it something you've discussed further internally? @coetry |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue, my app has video over WebRTC and asking someone on a call to refresh to load the latest application because the chunks are now missing from the CDN would be very disruptive. I would prefer to have a setting, for example:
|
Beta Was this translation helpful? Give feedback.
-
|
An official answer to this from the Vercel team anno 2022 would be great. It's forcing us to only do nightly deploys (we don't have an international audience) unless we want to bother users with update popups and potentially losing state. |
Beta Was this translation helpful? Give feedback.
-
|
I brought this up with our Engineering team and we have it on our internal list of requested features. Thank you all for sharing your blockers, workarounds, and ideas surrounding this feature request. This kind of information is very helpful as we plan new features! |
Beta Was this translation helpful? Give feedback.
-
|
Why I can no longer find this discussion?
…On Mon, Aug 29, 2022 at 1:56 PM Amy ***@***.***> wrote:
I brought this up with our Engineering team and we have it on our internal
list of requested features. Thank you all for sharing your blockers,
workarounds, and ideas surrounding this feature request. This kind of
information is very helpful as we plan new features!
—
Reply to this email directly, view it on GitHub
<https://github.com/orgs/vercel/discussions/4140#discussioncomment-3502679>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAO4CCTTYELOFPLXB3TOD3V3T2THANCNFSM4MPQZ4WA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
We're also very interested in this, having the old assets removed on every deploy is a PITA, it would be great if we could keep them for a few hours at least |
Beta Was this translation helpful? Give feedback.
-
|
My team would also benefit from this. |
Beta Was this translation helpful? Give feedback.
-
|
I am also having some many failed chunk loads because of this. A lot of sizable React apps requires code splitting and not being able to load chunks between deployments is really inconvenient. |
Beta Was this translation helpful? Give feedback.
-
|
This is a major problem for us as well, we use Odoo with keycdn and the only solution we found for a quick fix was to use cloudflare always on. It seems to provide this functionality, but I'd much have a solution with keycdn that delays stale file cleanup... |
Beta Was this translation helpful? Give feedback.
-
|
Good news, this is something that is now available in Next.js behind a feature flag and is fully supported on Vercel. We're calling this Skew Protection: https://vercel.com/blog/version-skew-protection |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm deploying a PWA with code splitting.
When the user already has the app open, and then the new deployment happens, and then tries to navigate to a route that requires an additional JS chunk, then the app would crash.
Is there a way to somehow make previously deployed versioned assets remain available after the new release (at least for some time), e.g. main.v1.js, main.v2.js etc.?
If not, how do you guys deploy web apps with code splitting?
AWS Amplify Console does it out of the box: all versioned assets from my previous deployments remain available (at least for some time, don't know for how long).
Beta Was this translation helpful? Give feedback.
All reactions