Debian Patches

Status for node-yarnpkg/4.1.0+dfsg-8

Patch Description Author Forwarded Bugs Origin Last update
fix-algoliasearch-client-javascript.patch Patch file for component algoliasearch-client-javascript
1. Stopped parallel execution of rollup
2. Stopped creation of type definitions due to unavailable
dependencies
3. Removed useless rollup plugin
4. Made the tsconfig typescript 6 proof: "baseUrl" and
"moduleResolution": "node" (node10) are deprecated and rejected with
TS5101/TS5107. "paths" no longer needs "baseUrl" as long as its targets are
relative, and "bundler" is the only resolution accepted by both typescript 5
and 6 for an esnext module target.		 no
fix-yarnpkg-builder.patch Patch file for @yarnpkg/builder
1. Replaced esbuild with esbuild-wasm (see
@yarnpkg/builder/package.json)		 no
remove-cross-spawn.patch Replaced cross-spawn with spawn from node:child_process no
rename-lodash-import.patch Fixed import names of lodash packages no
fix-rollup-plugin-node-globals.patch Patch file for component rollup-plugin-node-globals
1. Fixed import names		 no
fix-patch-console.patch Patch file for component patch-console
1. Copied content from extended tsconfig
2. Forced cjs import of sinon
3. Made the inlined tsconfig typescript 6 proof: typescript 6 no longer scans
node_modules/@types by itself, so "node" has to be named in "types" (without
it, "node:stream" is TS2591 and the global console loses its Console
property); "moduleResolution": "node" (node10) is deprecated and rejected
with TS5107, "bundler" is the only value accepted by both typescript 5 and
6 for an ES module target and resolves nothing here anyway (the only import
is a node builtin); and the common source directory is now computed
differently, hence the explicit "rootDir" (TS5011).		 no
fix-yoga-wasm-web.patch Patch file for component yoga-wasm-web
1. Stop using closure compiler in emscripten (Debian
version is too old)
2. Removed dependency on unpackaged rollup plugin
3. Replcaed vitest with jest in tests
4. Drop -sUSE_ES6_IMPORT_META=0: emscripten no longer supports disabling
import.meta (it is now a legacy setting whose only accepted value is 1),
so emcc failed with "invalid command line setting"
5. Build with -std=c++17 instead of -std=c++14: emscripten's embind headers
(bind.h, val.h, wire.h) now use std::optional, std::apply,
std::disjunction and std::is_pointer_v, none of which exist in C++14
6. Drop -sTEXTDECODER=0: emscripten only accepts 1 or 2 now ("Setting this
zero to avoid even conditional usage of TextDecoder is no longer
supported"), so libstrings.js aborted the JS generation step
7. Read the asm.js module back from the object passed to the factory instead
of from its return value. Emscripten now emits the MODULARIZE factory as an
`async function`, so it returns a promise even under
WASM_ASYNC_COMPILATION=0, and wrapAsm() was handed a promise instead of the
module ("Cannot read properties of undefined (reading 'prototype')" in all
ink tests). Awaiting is not an option here: point 2 above switched ink to
the sync build precisely because top level await is unsupported in the iife
bundle. The factory still initialises synchronously and starts with
`var Module = moduleArg`, so the object handed in is the module itself.
8. Switch the test tsconfig to "moduleResolution": "bundler": node10 is
deprecated in typescript 6 and rejected with TS5107, and "bundler" is the
only value accepted by both typescript 5 and 6 for an ES module target.
Name "node" in "types" too, since typescript 6 no longer scans
node_modules/@types by itself and the tests import node builtins		 no
fix-ink.patch Patch file for component ink
1. Copied contents from the extended tsconfig file
2. Switched to sync build of yoga-wasm-web since
top level await is unsupported for iife output
3. Excluded some tests
4. Fixed import for signal-exit
5. Forced cjs import of sinon
6. Added an explicit "rootDir": typescript 6 computes the common source
directory differently and refuses to guess it (TS5011). "src" is what
typescript 5 was inferring, so the output layout is unchanged.		 no
fix-alcalzone-ansi-tokenize.patch Patches for component alcalzone-ansi-tokenize
1. Copied contents from the extended tsconfig
file and removed an unsupported tsconfig
flag
2. Modified how tests are run. Instead of using
ava and tsnode, the typescript test files are
compiled and the js output is run using ava
3. Added explicit "rootDir" settings: typescript 6
computes the common source directory differently
and refuses to guess it (TS5011). The values are
the ones typescript 5 was inferring, so the
output layout is unchanged.		 no
fix-ink-text-input.patch Patch file for component ink-text-input
1. Copied contents from extended tsconfig file
2. Added an explicit "rootDir": typescript 6 computes the common source
directory differently and refuses to guess it (TS5011). "source" is what
typescript 5 was inferring, so the output layout is unchanged.		 no
force-chalk-require.patch Force use of chalk cjs (v4) instead of chalk esm (v5) no
fix-yarnpkg-parsers.patch Patch file for @yarnpkg/parsers
1. Fix to use newer version of js-yaml		 no
exclude-tests.patch Disabled some tests because:
1. Test dependency wasn't available (comment-json)
2. Some binaries which a test needed were excluded
3. Some tests only fail in test environment		 no
fix-yarnpkg-libzip.patch Patch file for @yarnpkg/libzip
1. Stop using docker
2. Use local copy of zlib-ng and @arcanis/libzip
instead of downloading from internet
3. Drop -sNODEJS_CATCH_EXIT=0 and -sNODEJS_CATCH_REJECTION=0: these settings
are no longer supported by emscripten (they are now listed in
LEGACY_SETTINGS) and, since this build also uses -sSTRICT=1, passing them
makes emcc fail with "legacy setting used in strict mode". Their removal
is a no-op here since 0 was the value being requested anyway.
4. Wait on each background emcc job individually: a plain "wait" always
returns 0, so an emcc failure used to be silently ignored and the build
only broke much later, when rollup could not resolve ./libzipSync.
5. Export HEAPU16 and HEAPU32 as runtime methods (HEAPU8 was already exported
here). Since 6.0.5 emscripten only emits the heap views it believes are
needed, but the LE_HEAP_UPDATE() helper that -sSUPPORT_BIG_ENDIAN=1 injects
assigns to HEAPU16 and HEAPU32 unconditionally, so the module aborted at
load time with "ReferenceError: HEAPU16 is not defined". Listing them in
EXPORTED_RUNTIME_METHODS forces them to be emitted again.
6. Read the sync module back from the object passed to the factory (sync.ts and
libzipSync.d.ts). Emscripten now emits the MODULARIZE factory as an
`async function`, so it returns a promise even under
WASM_ASYNC_COMPILATION=0, and makeInterface() was handed a promise instead
of the module ("TypeError: emZip._malloc is not a function"). getLibzipSync()
is synchronous by contract, so awaiting is not an option; the factory does
still initialise synchronously and starts with `var Module = moduleArg`, so
the object handed in is the module itself. async.ts already awaits and needs
no change.
7. Build with -sWASM_BIGINT=0. Emscripten now defaults to WASM_BIGINT=1, which
passes i64 arguments as a single JS BigInt instead of legalizing them into a
low/high pair of i32s. makeInterface() describes every 64 bit parameter as
the `number64` pair, so calls such as zip_source_buffer_create() failed with
"TypeError: Cannot convert 22 to a BigInt". Turning the setting off restores
the ABI the JS bindings are written against.		 no
fix-yarnpkg-core.patch Patch file for @yarnpkg/core
1. Renamed import isCI to isCIImport to fix naming conflict
with class field isCI (terser couldn't differentiate
between them)
2. Moved some contents of tgzUtils.ts to tgzUtilsExt.ts to
decouple the bundle output and the tgzUtils.ts file		 no
fix-yarnpkg-pnp.patch Patch file for @yarnpkg/pnp
1. Allowed rollup to find dependencies		 no
fix-arcanis-libzip.patch Patch file for component arcanis-libzip
1. Removed some files from the cmake build
which were excluded from the upstream tar-
ball		 no
fix-zlib-ng.patch fix-zlib-ng
Patch file for component zlib-ng
1. Edited make rules that depend on test/ folder
which was excluded from upstream tarball		 Debian Javascript Maintainers no 2026-03-04
disable-network-tests.patch Disable network tests We can't reliably test those during the build as the build environment
does not have Internet connection.		 Zixing Liu <zixing.liu@canonical.com> not-needed 2024-06-19
0020-Fix-cmake-error.patch Fix cmake error Bastien Roucariès <rouca@debian.org> not-needed 2026-03-04
fix-for-tar-7.patch add fix for node-tar >= 7 Xavier Guimard <yadd@debian.org> not-needed debian 2026-06-29
fix-jsonc-parser.patch fix jsonc-parser build with typescript 6 Patches for component jsonc-parser:
.
1. "module": "umd" and "moduleResolution": "node" (node10) are deprecated in
typescript 6 and rejected with TS5107. The umd wrapper is useless here:
the component is only ever loaded with require() (by
rollup-plugin-esbuild), so plain commonjs gives the same runtime
behaviour. Dropping "moduleResolution" keeps the implicit node10 lookup
under typescript 5 and is deprecation-free under 6.
2. typescript 6 no longer scans node_modules/@types automatically, so the
types used by src/test/*.ts have to be named explicitly.
3. esModuleInterop is enabled by default in typescript 6, which turns
"import * as assert" into a non callable namespace object (TS2349).
"import assert = require()" is callable and emits the same require() call
with both compilers.		 Xavier Guimard <yadd@debian.org> not-needed 2026-08-17

All known versions for source package 'node-yarnpkg'

Links