-
-
Notifications
You must be signed in to change notification settings - Fork 331
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
PurgeCSS Vite Plugin #2881
Comments
@endigo9740 anything blocking this one? I can give this a go if it's just porting the same markdown over, into an mdx file |
@phamduylong yeah @AdrianGonz97 is the author of the plugin and was going to confirm it works for all supported meta-frameworks listed above. This may need additional effort now that Vite 6 has been released. So we'll need his thumbs up before we can progress on this. |
I will update this comment along the way. Updates Needed
This will work: npx [email protected] init -p Additional NoteIt would be helpful to add documentation regarding TailwindCSS Framework Compatibility
|
@AdrianGonz97 just pinging you here to make sure you're aware. This is great news though! |
Link to the Page
Describe the Issue (screenshots encouraged!)
We need to verify this plugin is working with Skeleton v3. It can help dramatically decrease bundle sizes by purging unwanted CSS in the bundle. However there is some uncertainty on whether it will work, especially with the Vite 6 release recently
How to Test
For the initial test we'll ONLY test SvelteKit as we know it was working before in v2. Do the following:
npm run build
command and view the size of the CSS bundle. It should be listed in the console during this process.Handling the Results
There's two outcomes here:
Follow Up Test
If it works in SvelteKit, ensure we've tested it in all Vite-based frameworks, including:
Note that Next.js uses Webpack/Turbopack, not Vite, and will not qualify for this test.
Reporting the Results
When tests are complete, ping me here (Chris) as well as @AdrianGonz97 (CokaKoala on Discord) to share the results. Adrian is the original author and can address any issues that might arise.
The text was updated successfully, but these errors were encountered: