Add Content-Security-Policy to Svelte config #1079
Merged
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.
See https://kbse.atlassian.net/browse/LWS-215
Protects against XSS (among other things). https://kit.svelte.dev/docs/configuration#csp
Svelte automatically adds/sets nonces:
I don't like style-src's
unsafe-inline
, but Svelte adds it automatically anyway; perhaps it can't (at this point) work without it. There's an open issue: sveltejs/kit#11747I set style-src explicitly in
svelte.config.js
because otherwise, for some reason,unsafe-inline
is not automatically added when running the integration tests, resulting in two tests failing.