nextjs - 💡(How to fix) Fix Docs: Docs incorrectly say that SRI is not available in turbopack [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#91718Fetched 2026-04-08 01:07:18
View on GitHub
Comments
3
Participants
3
Timeline
7
Reactions
0
Timeline (top)
commented ×3closed ×1issue_type_added ×1labeled ×1
RAW_BUFFERClick to expand / collapse

What is the documentation issue?

According to this blog, https://nextjs.org/blog/next-16-2-turbopack#subresource-integrity-support , Subresource Integrity Support is now supported with Turbopack in the latest version. I also verified it on my app and it works.

That makes this docs page incorrect. It says:

Limitations of SRI ... Webpack only: Not available with Turbopack ...

Should we proceed by saying in which nextjs version it's supported with turbopack or just straight up delete that line?

Is there any context that might help us understand?

(No context needed)

Does the docs page already exist? Please link to it.

https://nextjs.org/docs/app/guides/content-security-policy

extent analysis

Fix Plan

To fix the outdated documentation, we need to update the "Limitations of SRI" section.

  • Remove the line "Webpack only: Not available with Turbopack" from the documentation.
  • Alternatively, add a note specifying the version of Next.js that supports Subresource Integrity with Turbopack, for example:
> Limitations of SRI
> ...
> Note: Support for Turbopack was added in Next.js 16.2.
  • If the version needs to be highlighted, it can be done as follows:
> Limitations of SRI
> ...
> Available with Webpack and Turbopack (supported since Next.js 16.2)

Verification

To verify the fix, check the updated documentation page at https://nextjs.org/docs/app/guides/content-security-policy and ensure the "Limitations of SRI" section reflects the correct information about Turbopack support.

Extra Tips

When updating documentation, it's essential to ensure that the changes are accurate, clear, and consistent with the current state of the software. Additionally, consider adding version notes or changelogs to help users track changes and updates.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING