Add CSP-friendly Alpine build #3959
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
|
Hi, After test of 3.13.5 & 3.13.7, It seems that without the use of unsafe-eval is still mandatory. |
Contributor
|
@loicy using @alpinejs/csp ? Just to be clear. |
This was referenced Jul 10, 2024
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.
This PR provides a version of AlpineJS that is compatible with strict content security policies that would otherwise prevent the usage of Alpine because of "unsafe-eval" violations.
It removes the ability to evaluate JavaScript expressions inside HTML attributes; however, it maintains ALL functionality of Alpine otherwise.
All plugins and features are CSP-compatible when using this build.