docs: fix CSP example to only include unsafe-eval in development #88407
Conversation
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
icyJoseph
approved these changes
Jan 12, 2026
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.
What
Fixes the CSP documentation "Without Nonces" example to only include
'unsafe-eval'in development mode.Why
The example was showing
'unsafe-eval'without a development check, which would cause it to be shipped to production. This is inconsistent with the guidance in the "Development vs Production Considerations" section which correctly shows how to conditionally add'unsafe-eval'only in development.How
Added a
isDevcheck usingprocess.env.NODE_ENV === 'development'and conditionally includes'unsafe-eval'in thescript-srcdirective only when in development mode.