feat(svelte-scoped): add hashSafelistClasses boolean, by default do not hash safelisted classes#5157
Merged
zyyv merged 2 commits intounocss:mainfrom Apr 7, 2026
Conversation
✅ Deploy Preview for unocss ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
commit: |
zyyv
approved these changes
Apr 7, 2026
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
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.
A bit unsure whether this is a new feature or a bug fix, calling it a feature for now.
This PR adds
hashSafelistClasses(default false) in the Svelte-scoped config which now by default removes hashing of safelisted classes making it easier to use with classes that need to have specific names such as third party CSS. Note that this will make the names of safelisted classes very obvious in production.Previous behavior: Hash classes that are safelisted (may cause issues with third party CSS/animations)
New behavior: Don't hash classes that are safelisted (could be better when integrating with other CSS)
If the previous behavior is needed set
hashSafelistClassestotrue. I didn't touch the code for the previous behavior.fix #5154