Debian Patches
Status for node-ajv-keywords/5.1.0-7
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| fix-tsconfig-for-test.patch | fix tsconfig to import chai in test | Yadd <yadd@debian.org> | not-needed | 2021-11-24 | ||
| drop-uuid.patch | drop uuid dependency, use built-in crypto.randomUUID() uuid >= 12 is ESM-only and can no longer be loaded via require(). The only usage was for v4() (random UUIDs), which is identical to crypto.randomUUID() shipped with Node.js since 14.17. |
Xavier Guimard <yadd@debian.org> | not-needed | 2026-04-26 | ||
| ts6-jest-tsconfig.patch | fix build and tests with TypeScript 6 The root tsconfig.json gains an explicit "rootDir" (TypeScript 6 reports TS5011 and would emit into dist/src/ instead of dist/) and an explicit "types": ["node"] (no more automatic node_modules/@types scan, TS2591 on module and Buffer). Only @types/node is added there: @types/jest is marked "test" in debian/nodejs/extlinks, so a nocheck build would fail on it. . ts-jest defaults to the root tsconfig.json, which declares no "types". That was harmless with TypeScript 5, which scanned node_modules/@types automatically, but TypeScript 6 only walks the type roots when "types" contains the "*" wildcard, so the specs lose the node and jest globals (TS2591/TS2593 on require, __dirname, describe, it). . spec/tsconfig.json already declares "types": ["node", "jest"], so pointing ts-jest at it is enough. The types cannot simply be moved into the root tsconfig, which drives dh_auto_build without @types/jest linked. |
Xavier Guimard <yadd@debian.org> | not-needed | 2026-08-16 |