docs: Immutable static assets#95348
Open
mischnic wants to merge 4 commits into
Open
Conversation
Contributor
Tests PassedCommit: 0f86fd9 |
Contributor
Stats skippedCommit: 0f86fd9 |
sokra
reviewed
Jul 1, 2026
sokra
reviewed
Jul 1, 2026
sokra
approved these changes
Jul 1, 2026
icyJoseph
reviewed
Jul 1, 2026
icyJoseph
reviewed
Jul 1, 2026
icyJoseph
reviewed
Jul 1, 2026
icyJoseph
reviewed
Jul 1, 2026
7c9c1e7 to
a843c13
Compare
icyJoseph
reviewed
Jul 1, 2026
icyJoseph
reviewed
Jul 1, 2026
icyJoseph
reviewed
Jul 1, 2026
icyJoseph
reviewed
Jul 1, 2026
| > | ||
| > **Enabling this feature when your provider or adapter does not support it can result in broken deployments.** | ||
|
|
||
| Enabling skew protection means that all static assets are requested with a deployment-specific query parameter, e.g. |
Member
There was a problem hiding this comment.
Suggested change
| Enabling skew protection means that all static assets are requested with a deployment-specific query parameter, e.g. | |
| When skew protection is enabled, static asset requests include a deployment-specific query parameter, for example: |
icyJoseph
reviewed
Jul 1, 2026
| GET https://foo.com/_next/static/chunks/0d_ks0ow7ur6m.js?dpl=<unique-deployment-id> | ||
| ``` | ||
|
|
||
| One downside of this is that browsers have to download even unchanged static assets again after a new deployment. |
Member
There was a problem hiding this comment.
Suggested change
| One downside of this is that browsers have to download even unchanged static assets again after a new deployment. | |
| One downside is that browsers have to download static assets again after each new deployment, even when those assets have not changed. |
icyJoseph
reviewed
Jul 1, 2026
|
|
||
| One downside of this is that browsers have to download even unchanged static assets again after a new deployment. | ||
|
|
||
| Immutable static assets is a feature that enables omitting the `?dpl` query parameter for static assets that are guaranteed to be immutable and content-addressed by their filename, allowing browsers to cache them indefinitely. It also enables not uploading unchanged static assets again after a new deployment: |
Member
There was a problem hiding this comment.
Suggested change
| Immutable static assets is a feature that enables omitting the `?dpl` query parameter for static assets that are guaranteed to be immutable and content-addressed by their filename, allowing browsers to cache them indefinitely. It also enables not uploading unchanged static assets again after a new deployment: | |
| Immutable static assets allow the `?dpl` query parameter to be omitted for static assets that are guaranteed to be immutable and content-addressed by their filename. This lets browsers cache those assets indefinitely and allows unchanged static assets to be skipped when uploading files during subsequent deployments: |
icyJoseph
reviewed
Jul 1, 2026
| GET https://foo.com/_next/static/immutable/chunks/0d_ks0ow7ur6m.js | ||
| ``` | ||
|
|
||
| You can use this config option to opt out of immutable static assets (when your adapter enabled it, otherwise this has no effect): |
Member
There was a problem hiding this comment.
Suggested change
| You can use this config option to opt out of immutable static assets (when your adapter enabled it, otherwise this has no effect): | |
| You can use this config option to opt out of immutable static assets when your adapter has enabled support for them. If your adapter has not enabled this feature, this option has no effect: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.