You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is code to order css that is imported in a deterministic order based on the order that it is imported into files. This works great when there is only 1 input file, but when multiple input files are used in rollup, then the output ends up putting all css from the non-first inputs at the top in resolve order (as long as it is not as well imported into the first input). This creates inconsistent outputs that can cause overrides to work incorrectly.
Summary
There is code to order css that is imported in a deterministic order based on the order that it is imported into files. This works great when there is only 1 input file, but when multiple input files are used in rollup, then the output ends up putting all css from the non-first inputs at the top in resolve order (as long as it is not as well imported into the first input). This creates inconsistent outputs that can cause overrides to work incorrectly.
Replication
https://stackblitz.com/edit/vitejs-vite-bgp6mc?file=rollup.config.js&view=editor
npm run build
Expected Results
The resulting
dist/index.css
should not put the css from the second input before the shared css.Actual Results
The second inputs non-shared css is placed first, and then everything is ordered as intended.
The text was updated successfully, but these errors were encountered: