[Regression] v8 wasm error when running yarn install with yarn v3+

[kxxt]

V8 Bug report: https://issues.chromium.org/issues/360030990 (Unfortunately not visible to public)

Running yarn install with https://github.com/hedgedoc/hedgedoc produces lots of unexpected errors:

➤ YN0000: ┌ Resolution step
➤ YN0060: │ HedgeDoc@workspace:. provides sequelize (p91ea1) with version 5.22.5, which doesn't satisfy what connect-session-sequelize requests
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 3s 448ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ @aashutoshrathi/word-wrap@npm:1.2.6 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/code-frame@npm:7.22.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/helper-validator-identifier@npm:7.22.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/highlight@npm:7.22.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @braintree/sanitize-url@npm:6.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/code-frame@npm:7.22.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/helper-validator-identifier@npm:7.22.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/highlight@npm:7.22.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @braintree/sanitize-url@npm:6.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @colors/colors@npm:1.5.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/helper-validator-identifier@npm:7.22.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/highlight@npm:7.22.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @braintree/sanitize-url@npm:6.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @colors/colors@npm:1.5.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @dabh/diagnostics@npm:2.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @babel/highlight@npm:7.22.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @braintree/sanitize-url@npm:6.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @colors/colors@npm:1.5.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @dabh/diagnostics@npm:2.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @discoveryjs/json-ext@npm:0.5.7 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @braintree/sanitize-url@npm:6.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @colors/colors@npm:1.5.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @dabh/diagnostics@npm:2.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @discoveryjs/json-ext@npm:0.5.7 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @esbuild/linux-riscv64@npm:0.17.19 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @colors/colors@npm:1.5.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @dabh/diagnostics@npm:2.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @discoveryjs/json-ext@npm:0.5.7 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @esbuild/linux-riscv64@npm:0.17.19 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint-community/eslint-utils@npm:4.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @dabh/diagnostics@npm:2.0.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @discoveryjs/json-ext@npm:0.5.7 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @esbuild/linux-riscv64@npm:0.17.19 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint-community/eslint-utils@npm:4.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint-community/regexpp@npm:4.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @discoveryjs/json-ext@npm:0.5.7 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @esbuild/linux-riscv64@npm:0.17.19 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint-community/eslint-utils@npm:4.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint-community/regexpp@npm:4.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint/eslintrc@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @esbuild/linux-riscv64@npm:0.17.19 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint-community/eslint-utils@npm:4.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint-community/regexpp@npm:4.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint/eslintrc@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint/js@npm:8.46.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint-community/eslint-utils@npm:4.4.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint-community/regexpp@npm:4.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint/eslintrc@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint/js@npm:8.46.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @gar/promisify@npm:1.1.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint-community/regexpp@npm:4.6.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint/eslintrc@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint/js@npm:8.46.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @gar/promisify@npm:1.1.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @hedgedoc/codemirror-5@npm:5.65.12 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint/eslintrc@npm:2.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint/js@npm:8.46.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @gar/promisify@npm:1.1.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @hedgedoc/codemirror-5@npm:5.65.12 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/config-array@npm:0.11.10 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @eslint/js@npm:8.46.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @gar/promisify@npm:1.1.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @hedgedoc/codemirror-5@npm:5.65.12 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/config-array@npm:0.11.10 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/module-importer@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @gar/promisify@npm:1.1.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @hedgedoc/codemirror-5@npm:5.65.12 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/config-array@npm:0.11.10 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/module-importer@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/object-schema@npm:1.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @hedgedoc/codemirror-5@npm:5.65.12 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/config-array@npm:0.11.10 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/module-importer@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/object-schema@npm:1.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @isaacs/cliui@npm:8.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/config-array@npm:0.11.10 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/module-importer@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/object-schema@npm:1.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @isaacs/cliui@npm:8.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @mapbox/node-pre-gyp@npm:1.0.11 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/module-importer@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/object-schema@npm:1.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @isaacs/cliui@npm:8.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @mapbox/node-pre-gyp@npm:1.0.11 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/core@npm:3.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @humanwhocodes/object-schema@npm:1.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @isaacs/cliui@npm:8.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @mapbox/node-pre-gyp@npm:1.0.11 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/core@npm:3.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/date-skeleton@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @isaacs/cliui@npm:8.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @mapbox/node-pre-gyp@npm:1.0.11 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/core@npm:3.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/date-skeleton@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/number-skeleton@npm:1.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @mapbox/node-pre-gyp@npm:1.0.11 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/core@npm:3.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/date-skeleton@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/number-skeleton@npm:1.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/parser@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/core@npm:3.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/date-skeleton@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/number-skeleton@npm:1.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/parser@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/runtime@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/date-skeleton@npm:1.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/number-skeleton@npm:1.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/parser@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/runtime@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.scandir@npm:2.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/number-skeleton@npm:1.2.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/parser@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/runtime@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.scandir@npm:2.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.stat@npm:2.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/parser@npm:5.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/runtime@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.scandir@npm:2.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.stat@npm:2.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.walk@npm:1.2.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @messageformat/runtime@npm:3.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.scandir@npm:2.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.stat@npm:2.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.walk@npm:1.2.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @npmcli/config@npm:6.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.scandir@npm:2.1.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.stat@npm:2.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.walk@npm:1.2.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @npmcli/config@npm:6.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @npmcli/fs@npm:1.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.stat@npm:2.0.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.walk@npm:1.2.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @npmcli/config@npm:6.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @npmcli/fs@npm:1.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @npmcli/fs@npm:3.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @nodelib/fs.walk@npm:1.2.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @npmcli/config@npm:6.2.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @npmcli/fs@npm:1.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @npmcli/fs@npm:3.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @npmcli/map-workspaces@npm:3.0.4 can't be found in the cache and will be fetched from the remote registry
➤ YN0001: │ Libzip Error: Read error: No error information
    at ZipFS.makeLibzipError ([worker eval]:1:30482)
    at new ZipFS ([worker eval]:1:29887)
    at MessagePort.<anonymous> ([worker eval]:1:468472)
➤ YN0013: │ @npmcli/move-file@npm:1.1.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0001: │ Libzip Error: Read error: No error information
    at ZipFS.makeLibzipError ([worker eval]:1:30482)
    at new ZipFS ([worker eval]:1:29887)
    at MessagePort.<anonymous> ([worker eval]:1:468472)
➤ YN0001: │ Libzip Error: Read error: No error information
    at ZipFS.makeLibzipError ([worker eval]:1:30482)
    at new ZipFS ([worker eval]:1:29887)
    at MessagePort.<anonymous> ([worker eval]:1:468472)
➤ YN0001: │ Libzip Error: Read error: No error information
    at ZipFS.makeLibzipError ([worker eval]:1:30482)
    at new ZipFS ([worker eval]:1:29887)
    at MessagePort.<anonymous> ([worker eval]:1:468472)
➤ YN0013: │ @npmcli/name-from-folder@npm:2.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @passport-next/passport-openid@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @passport-next/passport-strategy@npm:1.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0001: │ Libzip Error: Read error: No error information
    at ZipFS.makeLibzipError ([worker eval]:1:30482)
    at new ZipFS ([worker eval]:1:29887)
    at MessagePort.<anonymous> ([worker eval]:1:468472)

#
# Fatal JavaScript out of memory: MemoryChunk allocation failed during deserialization.
#
----- Native stack trace -----

➤ YN0013: │ @pkgjs/parseargs@npm:0.11.0 can't be found in the cache and will be fetched from the remote registry
 1: 0x3125d2e38c  [/usr/bin/node]
 2: 0x3126b4d750 v8::base::FatalOOM(v8::base::OOMType, char const*) [/usr/bin/node]
 3: 0x3125ec4252 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
 4: 0x3125ec4438 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
 5: 0x31260aa89a  [/usr/bin/node]
 6: 0x31260f9b9e v8::internal::MemoryAllocator::AllocateAlignedMemory(unsigned long, unsigned long, unsigned long, v8::internal::AllocationSpace, v8::internal::Executability, void*, v8::internal::VirtualMemory*) [/usr/bin/node]
 7: 0x31260f9d7a v8::internal::MemoryAllocator::AllocateUninitializedChunkAt(v8::internal::BaseSpace*, unsigned long, v8::internal::Executability, unsigned long, v8::internal::PageSize) [/usr/bin/node]
➤ YN0001: │ Libzip Error: Read error: No error information
    at ZipFS.makeLibzipError ([worker eval]:1:30482)
    at new ZipFS ([worker eval]:1:29887)
    at MessagePort.<anonymous> ([worker eval]:1:468472)
 8: 0x31260fa23a v8::internal::MemoryAllocator::AllocatePage(v8::internal::MemoryAllocator::AllocationMode, v8::internal::Space*, v8::internal::Executability) [/usr/bin/node]
➤ YN0013: │ @tokenizer/token@npm:0.3.0 can't be found in the cache and will be fetched from the remote registry
 9: 0x3126108d64 v8::internal::SemiSpace::Commit() [/usr/bin/node]
10: 0x312610a174 v8::internal::SemiSpaceNewSpace::SemiSpaceNewSpace(v8::internal::Heap*, unsigned long, unsigned long) [/usr/bin/node]
11: 0x31260bd7b6 v8::internal::Heap::SetUpSpaces(v8::internal::LinearAllocationArea&, v8::internal::LinearAllocationArea&) [/usr/bin/node]
12: 0x312602d8b8 v8::internal::Isolate::Init(v8::internal::SnapshotData*, v8::internal::SnapshotData*, v8::internal::SnapshotData*, bool) [/usr/bin/node]
13: 0x312602e7b8 v8::internal::Isolate::InitWithSnapshot(v8::internal::SnapshotData*, v8::internal::SnapshotData*, v8::internal::SnapshotData*, bool) [/usr/bin/node]
14: 0x3126453de2 v8::internal::Snapshot::Initialize(v8::internal::Isolate*) [/usr/bin/node]
15: 0x3125ed9ec2 v8::Isolate::Initialize(v8::Isolate*, v8::Isolate::CreateParams const&) [/usr/bin/node]
16: 0x3125bdb1ea node::NewIsolate(v8::Isolate::CreateParams*, uv_loop_s*, node::MultiIsolatePlatform*, node::SnapshotData const*, node::IsolateSettings const&) [/usr/bin/node]
17: 0x3125dc97cc node::worker::WorkerThreadData::WorkerThreadData(node::worker::Worker*) [/usr/bin/node]
18: 0x3125dc7b80 node::worker::Worker::Run() [/usr/bin/node]
19: 0x3125dc8902  [/usr/bin/node]
20: 0x32ba48cb3e  [/usr/lib/libc.so.6]
21: 0x32ba4da064  [/usr/lib/libc.so.6]

Test results on different version:

(To test with electron, rename electron to node and set ELECTRON_RUN_AS_NODE)

nodejs            v20.16.0  v8 11.3.8.224                is ok
nodejs            v22.6.0   v8 12.4.21.254               is bad
electron v31.4.0  v20.16.0  v8 12.6.228.30-electron.0    
electron v30.3.1  v20.15.1  v8 12.4.254.20-electron.0    is bad
electron v29.4.5  v20.9.0   v8 12.2.281.27-electron.0    is good

Current bisection range: 12.2.281.27..12.4.254.20 (968 commits in total)

[kxxt]

Other errors occurred in another run:

➤ YN0001: │ RangeError: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory for new instance
    at z ([worker eval]:1:281464)
    at [worker eval]:1:330026
    at e ([worker eval]:1:330043)
    at getLibzipSync ([worker eval]:1:338279)
    at getLibzipPromise ([worker eval]:1:338341)
    at MessagePort.<anonymous> ([worker eval]:1:468508)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:816:20)
    at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)
failed to compile wasm module: RangeError: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory for new instance
➤ YN0001: │ RangeError: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory for new instance
    at z ([worker eval]:1:281464)
    at [worker eval]:1:330026
    at e ([worker eval]:1:330043)
    at getLibzipSync ([worker eval]:1:338279)
    at getLibzipPromise ([worker eval]:1:338341)
    at MessagePort.<anonymous> ([worker eval]:1:468508)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:816:20)
    at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)
➤ YN0013: │ @types/content-disposition@npm:0.5.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/cookies@npm:0.7.7 can't be found in the cache and will be fetched from the remote registry
failed to compile wasm module: RangeError: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory for new instance
➤ YN0001: │ RangeError: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory for new instance
    at z ([worker eval]:1:281464)
    at [worker eval]:1:330026
    at e ([worker eval]:1:330043)
    at getLibzipSync ([worker eval]:1:338279)
    at getLibzipPromise ([worker eval]:1:338341)
    at MessagePort.<anonymous> ([worker eval]:1:468508)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:816:20)
    at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)
failed to compile wasm module: RangeError: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory for new instance
➤ YN0013: │ @types/debug@npm:4.1.8 can't be found in the cache and will be fetched from the remote registry
➤ YN0001: │ RangeError: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory for new instance
    at z ([worker eval]:1:281464)
    at [worker eval]:1:330026
    at e ([worker eval]:1:330043)
    at getLibzipSync ([worker eval]:1:338279)
    at getLibzipPromise ([worker eval]:1:338341)
    at MessagePort.<anonymous> ([worker eval]:1:468508)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:816:20)
    at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)
➤ YN0013: │ @types/estree-jsx@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
failed to compile wasm module: RangeError: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory for new instance
➤ YN0001: │ RangeError: WebAssembly.Instance(): Out of memory: Cannot allocate Wasm memory for new instance
    at z ([worker eval]:1:281464)
    at [worker eval]:1:330026
    at e ([worker eval]:1:330043)
    at getLibzipSync ([worker eval]:1:338279)
    at getLibzipPromise ([worker eval]:1:338341)
    at MessagePort.<anonymous> ([worker eval]:1:468508)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:816:20)
    at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)