-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
fix(css): scoped css order with non-scoped css #19678
Conversation
Co-authored-by: bluwy <bjornlu.dev@gmail.com>
/ecosystem-ci run |
commit: |
This comment was marked as outdated.
This comment was marked as outdated.
📝 Ran ecosystem CI on ✅ histoire, rakkas, analogjs, qwik, previewjs, astro, nuxt, ladle, marko, vite-setup-catalogue, waku, sveltekit, laravel, vitest, quasar, vite-environment-examples, vite-plugin-vue, vite-plugin-react, react-router, vite-plugin-cloudflare, vite-plugin-react-swc, vitepress, unocss, vite-plugin-svelte, vite-plugin-pwa, vike, vuepress, storybook |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good to me if we want to go with a different implementation, and we could see how well it works and polish again 👍
Description
This PR changes the implementation of
cssScopeTo
support to the one proposed in #16058 from #19418.The implementation in #19418 has a upside of a better chunking behavior, but had a downside of not preserving the style order when a single module has both scoped and non-scoped styles.
refs https://discord.com/channels/804011606160703521/804439875226173480/1349606289252028418
refs withastro/astro#13420