Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency node to v20 #692

Merged
merged 1 commit into from
Jul 10, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 24, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) major 18.19.0 -> 20.15.1 age adoption passing confidence
@types/node (source) devDependencies minor 20.11.24 -> 20.14.10 age adoption passing confidence

Release Notes

nodejs/node (node)

v20.15.1

Compare Source

v20.15.0: 2024-06-20, Version 20.15.0 'Iron' (LTS), @​marco-ippolito

Compare Source

test_runner: support test plans

It is now possible to count the number of assertions and subtests that are expected to run within a test. If the number of assertions and subtests that run does not match the expected count, the test will fail.

test('top level test', (t) => {
  t.plan(2);
  t.assert.ok('some relevant assertion here');
  t.subtest('subtest', () => {});
});

Contributed by Colin Ihrig in #​52860

inspector: introduce the --inspect-wait flag

This release introduces the --inspect-wait flag, which allows debugger to wait for attachement. This flag is useful when you want to debug the code from the beginning. Unlike --inspect-brk, which breaks on the first line, this flag waits for debugger to be connected and then runs the code as soon as a session is established.

Contributed by Kohei Ueno in #​52734

zlib: expose zlib.crc32()

This release exposes the crc32() function from zlib to user-land.

It computes a 32-bit Cyclic Redundancy Check checksum of data. If
value is specified, it is used as the starting value of the checksum,
otherwise, 0 is used as the starting value.

The CRC algorithm is designed to compute checksums and to detect error
in data transmission. It's not suitable for cryptographic authentication.

const zlib = require('node:zlib');
const { Buffer } = require('node:buffer');

let crc = zlib.crc32('hello');  // 907060870
crc = zlib.crc32('world', crc);  // 4192936109

crc = zlib.crc32(Buffer.from('hello', 'utf16le'));  // 1427272415
crc = zlib.crc32(Buffer.from('world', 'utf16le'), crc);  // 4150509955

Contributed by Joyee Cheung in #​52692

cli: allow running wasm in limited vmem with --disable-wasm-trap-handler

By default, Node.js enables trap-handler-based WebAssembly bound
checks. As a result, V8 does not need to insert inline bound checks
int the code compiled from WebAssembly which may speedup WebAssembly
execution significantly, but this optimization requires allocating
a big virtual memory cage (currently 10GB). If the Node.js process
does not have access to a large enough virtual memory address space
due to system configurations or hardware limitations, users won't
be able to run any WebAssembly that involves allocation in this
virtual memory cage and will see an out-of-memory error.

$ ulimit -v 5000000
$ node -p "new WebAssembly.Memory({ initial: 10, maximum: 100 });"
[eval]:1
new WebAssembly.Memory({ initial: 10, maximum: 100 });
^

RangeError: WebAssembly.Memory(): could not allocate memory
    at [eval]:1:1
    at runScriptInThisContext (node:internal/vm:209:10)
    at node:internal/process/execution:118:14
    at [eval]-wrapper:6:24
    at runScript (node:internal/process/execution:101:62)
    at evalScript (node:internal/process/execution:136:3)
    at node:internal/main/eval_string:49:3

--disable-wasm-trap-handler disables this optimization so that
users can at least run WebAssembly (with a less optimial performance)
when the virtual memory address space available to their Node.js
process is lower than what the V8 WebAssembly memory cage needs.

Contributed by Joyee Cheung in #​52766

Other Notable Changes
Commits

v20.14.0

Compare Source

v20.13.1: 2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Compare Source

2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Revert "tools: install npm PowerShell scripts on Windows"

Due to a regression in the npm installation on Windows, this commit reverts the change that installed npm PowerShell scripts on Windows.

Commits
  • [b7d80802cc] - Revert "tools: install npm PowerShell scripts on Windows" (marco-ippolito) #​52897

v20.13.0

Compare Source

v20.12.2: 2024-04-10, Version 20.12.2 'Iron' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes
  • CVE-2024-27980 - Command injection via args parameter of child_process.spawn without shell option enabled on Windows
Commits

v20.12.1

Compare Source

v20.12.0

Compare Source

v20.11.1

Compare Source

v20.11.0

Compare Source

v20.10.0

Compare Source

v20.9.0

Compare Source

v20.8.1: 2023-10-13, Version 20.8.1 (Current), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes

The following CVEs are fixed in this release:

More detailed information on each of the vulnerabilities can be found in October 2023 Security Releases blog post.

Commits

v20.8.0: 2023-09-28, Version 20.8.0 (Current), @​ruyadorno

Compare Source

Notable Changes
Stream performance improvements

Performance improvements to writable and readable streams, improving the creation and destruction by ±15% and reducing the memory overhead each stream takes in Node.js

Contributed by Benjamin Gruenbaum in #​49745 and Raz Luvaton in #​49834.

Performance improvements for readable webstream, improving readable stream async iterator consumption by ±140% and improving readable stream pipeTo consumption by ±60%

Contributed by Raz Luvaton in #​49662 and #​49690.

Rework of memory management in vm APIs with the importModuleDynamically option

This rework addressed a series of long-standing memory leaks and use-after-free issues in the following APIs that support importModuleDynamically:

  • vm.Script
  • vm.compileFunction
  • vm.SyntheticModule
  • vm.SourceTextModule

This should enable affected users (in particular Jest users) to upgrade from older versions of Node.js.

Contributed by Joyee Cheung in #​48510.

Other notable changes
Commits

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Oct 24, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
svg-crowbar ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 8, 2024 8:00pm

@renovate renovate bot force-pushed the renovate/node-20.x branch from 0936090 to 13479f7 Compare October 24, 2023 17:24
@renovate renovate bot force-pushed the renovate/node-20.x branch from 13479f7 to d90678e Compare November 13, 2023 20:36
@renovate renovate bot force-pushed the renovate/node-20.x branch from d90678e to 909bee9 Compare November 22, 2023 15:24
@renovate renovate bot force-pushed the renovate/node-20.x branch from 909bee9 to 0e3a146 Compare January 9, 2024 21:58
@renovate renovate bot force-pushed the renovate/node-20.x branch from 0e3a146 to 24484c3 Compare February 14, 2024 07:19
@renovate renovate bot force-pushed the renovate/node-20.x branch from 24484c3 to 7a83a92 Compare February 14, 2024 19:22
@renovate renovate bot force-pushed the renovate/node-20.x branch from 7a83a92 to cc040a4 Compare March 26, 2024 19:28
@renovate renovate bot force-pushed the renovate/node-20.x branch from cc040a4 to ec373ff Compare April 3, 2024 16:16
@renovate renovate bot force-pushed the renovate/node-20.x branch from ec373ff to c3538bd Compare April 10, 2024 18:45
@renovate renovate bot force-pushed the renovate/node-20.x branch from c3538bd to 166e6d8 Compare May 7, 2024 17:49
@renovate renovate bot force-pushed the renovate/node-20.x branch from 166e6d8 to 53d8624 Compare May 9, 2024 15:07
@renovate renovate bot force-pushed the renovate/node-20.x branch from 53d8624 to 8baecdb Compare May 20, 2024 08:21
@renovate renovate bot force-pushed the renovate/node-20.x branch from 8baecdb to 8ac9dfa Compare May 20, 2024 16:49
@renovate renovate bot force-pushed the renovate/node-20.x branch from 8ac9dfa to 2ea3b37 Compare May 23, 2024 15:57
@renovate renovate bot force-pushed the renovate/node-20.x branch from 4db07c7 to 2c705f7 Compare June 5, 2024 11:10
@renovate renovate bot force-pushed the renovate/node-20.x branch from 2c705f7 to b332799 Compare June 17, 2024 22:33
@renovate renovate bot force-pushed the renovate/node-20.x branch from b332799 to f4d5efa Compare June 18, 2024 01:23
@renovate renovate bot force-pushed the renovate/node-20.x branch from f4d5efa to e5d1f1c Compare June 18, 2024 07:50
@renovate renovate bot force-pushed the renovate/node-20.x branch from e5d1f1c to 7d9bbca Compare June 19, 2024 17:22
@renovate renovate bot force-pushed the renovate/node-20.x branch from 7d9bbca to 9a77621 Compare June 20, 2024 16:26
@renovate renovate bot force-pushed the renovate/node-20.x branch from 9a77621 to 9819aa3 Compare June 20, 2024 22:57
@renovate renovate bot force-pushed the renovate/node-20.x branch from 9819aa3 to 633b286 Compare June 22, 2024 10:53
@renovate renovate bot force-pushed the renovate/node-20.x branch from 633b286 to c1008bd Compare June 25, 2024 04:15
@renovate renovate bot force-pushed the renovate/node-20.x branch from c1008bd to 39a827b Compare June 25, 2024 22:38
@renovate renovate bot force-pushed the renovate/node-20.x branch from 39a827b to 42b650c Compare July 3, 2024 00:32
@renovate renovate bot force-pushed the renovate/node-20.x branch from 42b650c to 292fce4 Compare July 5, 2024 21:39
@renovate renovate bot force-pushed the renovate/node-20.x branch from 292fce4 to ce20d91 Compare July 8, 2024 20:00
@cy6erskunk cy6erskunk merged commit 1737bae into master Jul 10, 2024
7 checks passed
@cy6erskunk cy6erskunk deleted the renovate/node-20.x branch July 10, 2024 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant