Debian Patches
Status for node-rollup-pluginutils/5.0.2~ds+~2.8.2-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| fake-tsc-transpile.diff | fake tsc transpilation | Xavier Guimard <yadd@debian.org> | not-needed | 2020-03-13 | ||
| drop-legacy-plugins.patch | not-needed | |||||
| switch-test-from-ava-to-tape.diff | switch test from ava+tsc to tape (common JS) | Yadd <yadd@debian.org> | not-needed | 2022-10-10 | ||
| fix-for-rollup-3.patch | fix for rollup 3 | Yadd <yadd@debian.org> | not-needed | debian | 2022-10-27 | |
| ts6-cumulative.patch | build with TypeScript 6 @rollup/plugin-typescript pins ModuleResolutionKind.NodeJs itself whenever the resolved "module" is not Node16/NodeNext, so the node10 resolution cannot be avoided from a config file -- and tsc 6 turns it into the hard error TS5107. "ignoreDeprecations" is therefore the only way out that leaves the emitted bundles untouched. . tsc 6 also stopped scanning node_modules/@types on its own, hence the explicit "types"; and "skipLibCheck" keeps third-party declarations that do not compile under tsc 6 out of the way. . The legacy bundle is switched to @rollup/plugin-typescript as well: the rollup-plugin-typescript module it used is being dropped from Debian. The new plugin validates the options it is given, so the module kind, the output directory and the source maps have to be spelled out. Its CommonJS output also asks for "esModule" explicitly, since rollup only marks a bundle __esModule on its own when there is a default export and this one has none -- without it the flag the shipped file used to carry would disappear. |
Xavier Guimard <yadd@debian.org> | not-needed | debian | 2026-08-17 |
All known versions for source package 'node-rollup-pluginutils'
- 5.0.2~ds+~2.8.2-2 (forky, sid)
- 5.0.2~ds+~2.8.2-1 (bookworm, trixie)