-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate off purify-css #10536
Comments
going to look into it now 🙏 |
So looking into it, I'm not sure why it's included in the tests when it's not included in the docs. #4710 has a comment about why you might need it:
What is the preferred solution here?
Will raise a PR for whatever is decided - tagging @Rich-Harris here too as he originally added this 🙏 |
|
I think using dropcss might be the best solution then as I'd prefer not to pull in a lot of dependencies and it'd be nice to demonstrate usage for our users. I filed an issue there requesting some types, but in the meantime we can just do If that doesn't work for some reason then my second choice would be to remove it and add a comment like:
|
Ty! I ended up writing types for the tests in #10546 so submitted a pr to dropcss to add those types in - hopefully they take a look at it soon 🤞 |
Closes #10536 Switch to using dropcss Add note about removing css in the docs Add note in docs about adding <html amp> as we don't do that anywhere. I also want to discourage people from using ⚡ since dropcss doesn't support it - people definitely will be using it so I've added a safeguard (.replace('⚡', 'amp')) --------- Co-authored-by: Puru Vijay <[email protected]> Co-authored-by: Simon H <[email protected]>
Describe the bug
purify-css
has not been updated in 6 years and is causing security warnings in the AMP exampleReproduction
kit/packages/kit/test/apps/amp/src/hooks.server.js
Line 25 in e133aba
Logs
No response
System Info
`master`
Severity
annoyance
Additional Information
Some alternatives:
The text was updated successfully, but these errors were encountered: