Allow unsafe-eval during development #55998
Merged
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
Fixes issue where a freshly cloned example will not work in development mode due to `unsafe-eval` being blocked by the CSP.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Fixes issue where a freshly cloned example will not work in development mode due to
unsafe-evalbeing blocked by the CSP.Currently, the example will not work in development. Running the example with
run devwill produce EvalError errors in console which prevent the app from functioning. This error also prevents any<Script>components withafterInteractivefrom being loaded. These issues do not occur in production whereevalis not used.This PR:
unsafe-evalif the environment is notproduction.script-srcvalue by allowing backwards compatibility with browsers that do not supportstrict-dynamic(https: http: 'unsafe-inline'will be ignored by browsers that supportstrict-dynamic).Some further details are available here: #55638. This PR is not a fix for the issue however.