Debian Patches
Status for node-rollup-plugin-sass/1.12.22-5
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| use-node-node-sass.patch | sass module is not packaged and needs packaging dart lang first | not-needed | 2022-07-28 | |||
| switch-from-ava-to-jest.patch | replace ava by jest | Yadd <yadd@debian.org> | not-needed | 2024-04-19 | ||
| ts6-compat.patch | fix build and tests with typescript 6 Drop the deprecated node10 resolution and downlevelIteration, set an explicit rootDir, spell out "strict": false (the sources were written for a non-strict compiler) and declare the type packages, which typescript 6 no longer picks up by scanning node_modules/@types. |
Xavier Guimard <yadd@debian.org> | not-needed | 2026-08-16 | ||
| deterministic-css-output-order.patch | make concatenated CSS output order deterministic The plugin collects the compiled styles by pushing them into `pluginState.styles` from its `transform` hook. Rollup runs `transform` hooks concurrently, so the order in which entries land in that array is the order in which the underlying `sass.render()` calls happen to settle, not the order in which the sass files are imported. Under load the two orders diverge, and `generateBundle` then hands over (or writes) the stylesheets concatenated in an arbitrary order. . That is a real bug for users - the cascade of the generated stylesheet becomes non-deterministic - and it makes the "should support output as function" test fail randomly, which shows up as a random FTBFS. . Sort the styles, in `generateBundle`, by their module's execution order, obtained by walking rollup's module graph depth first (post-order) from its entry points. The generated bundle's chunk `modules` can't be used for this: sass modules usually end up tree-shaken out of the chunk. |
Xavier Guimard <yadd@debian.org> | no | debian | 2026-08-17 |