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 node.js to v20 #354

Merged
merged 1 commit into from
Jul 10, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 21, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node final major 18 -> 20 age adoption passing confidence
@types/node (source) devDependencies major 18.15.13 -> 20.14.10 age adoption passing confidence

Release Notes

nodejs/node (node)

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: 2024-05-28, Version 20.14.0 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits

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: 2024-05-07, Version 20.13.0 'Iron' (LTS), @​marco-ippolito

Compare Source

2024-05-07, Version 20.13.0 'Iron' (LTS), @​marco-ippolito

buffer: improve base64 and base64url performance

The performance of the base64 and base64url encoding and decoding functions has been improved significantly.

Contributed by Yagiz Nizipli in #​52428

crypto: deprecate implicitly shortened GCM tags

This release, introduces a doc-only deprecation of using GCM authentication tags that are shorter than the cipher's block size, unless the user specified the authTagLength option.

Contributed by Tobias Nießen in #​52345

events,doc: mark CustomEvent as stable

From this release CustomEvent has been marked stable.

Contributed by Daeyeon Jeong in #​52618

fs: add stacktrace to fs/promises

Sync functions in fs throwed an error with a stacktrace which is helpful for debugging. But functions in fs/promises throwed an error without a stacktrace. This commit adds stacktraces by calling Error.captureStacktrace and re-throwing the error.

Contributed by 翠 / green in #​49849

report: add --report-exclude-network option

New option --report-exclude-network, also available as report.excludeNetwork, enables the user to exclude networking interfaces in their diagnostic report. On some systems, this can cause the report to take minutes to generate so this option can be used to optimize that.

Contributed by Ethan Arrowood in #​51645

src: add uv_get_available_memory to report and process

From this release it is possible to get the available memory in the system by calling process.getAvailableMemory().

Contributed by theanarkh #​52023

stream: support typed arrays

This commit adds support for typed arrays in streams.

Contributed by IlyasShabi #​51866

util: support array of formats in util.styleText

It is now possible to pass an array of format strings to util.styleText to apply multiple formats to the same text.

console.log(util.styleText(['underline', 'italic'], 'My italic underlined message'));

Contributed by Marco Ippolito in #​52040

v8: implement v8.queryObjects() for memory leak regression testing

This is similar to the queryObjects() console API provided by the Chromium DevTools console. It can be used to search for objects that have the matching constructor on its prototype chain in the heap after a full garbage collection, which can be useful for memory leak regression tests.
To avoid surprising results, users should avoid using this API on constructors whose implementation they don't control, or on constructors that can be invoked by other parties in the application.

To avoid accidental leaks, this API does not return raw references to the objects found. By default, it returns the count of the objects found. If options.format is 'summary', it returns an array containing brief string representations for each object. The visibility provided in this API is similar to what the heap snapshot provides, while users can save the cost of serialization and parsing and directly filer the target objects during the search.

We have been using this API internally for the test suite, which has been more stable than any other leak regression testing strategies in the CI. With a public implementation we can now use the public API instead.

const { queryObjects } = require('node:v8');
class A { foo = 'bar'; }
console.log(queryObjects(A)); // 0
let a = new A();
console.log(queryObjects(A)); // 1
// [ "A { foo: 'bar' }" ]
console.log(queryObjects(A, { format: 'summary' }));

// Release the object.
a = null;
// Search again. queryObjects() includes a full garbage collection
// so a should disappear.
console.log(queryObjects(A)); // 0

class B extends A { bar = 'qux'; }
// The child class B's prototype has A's prototype on its prototype chain
// so the prototype object shows up too.
console.log(queryObjects(A, { format: 'summary' })); // [ A {}' ]

Contributed by Joyee Cheung in #​51927

watch: mark as stable

From this release Watch Mode is considered stable.
When in watch mode, changes in the watched files cause the Node.js process to restart.

Contributed by Moshe Atlow in #​52074

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.

@renovate renovate bot changed the title chore(deps): update node.js to v20 chore(deps): update node.js to v20 - autoclosed Oct 20, 2023
@renovate renovate bot closed this Oct 20, 2023
@renovate renovate bot deleted the renovate/node-20.x branch October 20, 2023 00:10
@renovate renovate bot changed the title chore(deps): update node.js to v20 - autoclosed chore(deps): update node.js to v20 Oct 24, 2023
@renovate renovate bot reopened this Oct 24, 2023
@renovate renovate bot restored the renovate/node-20.x branch October 24, 2023 01:27
@renovate renovate bot changed the title chore(deps): update node.js to v20 chore(deps): update dependency @types/node to v20 Oct 24, 2023
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 5506bdb to 2141599 Compare October 25, 2023 18:07
@renovate renovate bot force-pushed the renovate/node-20.x branch from 2141599 to 5aec12c Compare October 31, 2023 09:13
@renovate renovate bot force-pushed the renovate/node-20.x branch from 5aec12c to 7c0dbf1 Compare November 7, 2023 22:51
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 5b2899b to d0f6ed1 Compare November 22, 2023 01:39
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from d95767d to 6b1713f Compare November 29, 2023 20:13
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from c8e8ed8 to b15463d Compare December 3, 2023 10:43
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20 chore(deps): update node.js to v20 Dec 3, 2023
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 1f91870 to f8451d4 Compare December 7, 2023 09:08
@renovate renovate bot force-pushed the renovate/node-20.x branch from f8451d4 to c334e65 Compare December 17, 2023 22:25
@renovate renovate bot force-pushed the renovate/node-20.x branch from c334e65 to 8e924be Compare December 30, 2023 04:39
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 4c99d64 to 295cab5 Compare January 11, 2024 07:04
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from af1f4d9 to 62413a3 Compare January 15, 2024 12:40
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 07ce83c to 4e222b1 Compare March 19, 2024 14:35
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 9324f73 to 6d24738 Compare April 5, 2024 23:13
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 362f83f to 847d7a2 Compare April 10, 2024 04:58
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from a4e4125 to 080cf75 Compare May 8, 2024 12:45
@renovate renovate bot force-pushed the renovate/node-20.x branch from 080cf75 to 08bedc1 Compare May 14, 2024 08:34
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from f9e79d8 to 17a96b5 Compare June 5, 2024 11:26
@renovate renovate bot force-pushed the renovate/node-20.x branch 6 times, most recently from 210d8e8 to 31ca2b2 Compare June 22, 2024 08:15
@renovate renovate bot force-pushed the renovate/node-20.x branch from 31ca2b2 to 15d14ae Compare June 25, 2024 22:46
@renovate renovate bot force-pushed the renovate/node-20.x branch from 15d14ae to 70ffd52 Compare July 5, 2024 21:43
@Benjamin-Park Benjamin-Park merged commit 5cf3511 into main Jul 10, 2024
6 checks passed
@Benjamin-Park Benjamin-Park deleted the renovate/node-20.x branch July 10, 2024 22:31
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