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.15.0 #185

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 19, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node final minor 20.14.0-buster-slim -> 20.15.0-buster-slim age adoption passing confidence
node stage minor 20.14.0-buster-slim -> 20.15.0-buster-slim age adoption passing confidence
@types/node (source) devDependencies minor 20.14.5 -> 20.17.12 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

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/node-20.x branch from c10fbce to f3713ae Compare June 20, 2024 23:31
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20.14.6 chore(deps): update dependency @types/node to v20.14.7 Jun 20, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20.14.7 chore(deps): update dependency @types/node to v20.14.8 Jun 22, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 34ca4cf to 540833a Compare June 25, 2024 01:15
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20.14.8 chore(deps): update node.js to v20.15.0 Jun 25, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 540833a to 270a015 Compare June 25, 2024 23:30
@renovate renovate bot force-pushed the renovate/node-20.x branch from 270a015 to effdfb8 Compare July 5, 2024 20:11
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 173dd9f to 8fa39f2 Compare July 23, 2024 18:25
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 0b70c9e to d46492c Compare August 2, 2024 11:16
@renovate renovate bot changed the title chore(deps): update node.js to v20.15.0 chore(deps): update node docker tag to v20.15.0 Aug 6, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from edd44e8 to 4cd2b26 Compare August 16, 2024 19:18
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 7b836c0 to 3d9940d Compare August 19, 2024 05:25
@renovate renovate bot force-pushed the renovate/node-20.x branch from 3d9940d to d5b4806 Compare August 28, 2024 02:03
@renovate renovate bot changed the title chore(deps): update node docker tag to v20.15.0 chore(deps): update node.js to v20.15.0 Aug 28, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 5cbb79c to 780064c Compare September 4, 2024 23:33
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 2e2e3b4 to 28c0b63 Compare September 27, 2024 16:50
@renovate renovate bot force-pushed the renovate/node-20.x branch from 28c0b63 to 51a7928 Compare October 8, 2024 00:19
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from d9e4d31 to cba49b6 Compare October 19, 2024 05:03
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 9ffedb4 to 92b5154 Compare October 28, 2024 21:25
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from cf3fa4a to d4844ca Compare November 3, 2024 07:05
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 759b7f4 to be470d8 Compare November 28, 2024 07:47
@renovate renovate bot force-pushed the renovate/node-20.x branch from be470d8 to 6d464f3 Compare December 11, 2024 11:07
@renovate renovate bot force-pushed the renovate/node-20.x branch from 6d464f3 to ec222bf Compare January 1, 2025 02:08
@renovate renovate bot force-pushed the renovate/node-20.x branch from ec222bf to 761b1c9 Compare January 6, 2025 10:51
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.

0 participants