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 all non-major dependencies #427

Merged
merged 1 commit into from
Jun 26, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 12, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@types/node (source) ^20.14.2 -> ^20.14.9 age adoption passing confidence devDependencies patch
c12 ^1.10.0 -> ^1.11.1 age adoption passing confidence devDependencies minor
eslint (source) ^9.4.0 -> ^9.5.0 age adoption passing confidence devDependencies minor
h3 ^1.11.1 -> ^1.12.0 age adoption passing confidence resolutions minor
h3 ^1.11.1 -> ^1.12.0 age adoption passing confidence devDependencies minor
node 20.14.0 -> 20.15.0 age adoption passing confidence image minor
pnpm (source) 9.3.0 -> 9.4.0 age adoption passing confidence packageManager minor
vue-tsc (source) ^2.0.21 -> ^2.0.22 age adoption passing confidence devDependencies patch
ws ^8.17.0 -> ^8.17.1 age adoption passing confidence devDependencies patch

Release Notes

unjs/c12 (c12)

v1.11.1

Compare Source

compare changes

🩹 Fixes
  • update: Await on onUpdate (6b37c98)
  • update: Respect falsy value of onCreate (cc4e991)
  • update: Use relative path to resolve config (8b58b25)
❤️ Contributors

v1.11.0

Compare Source

compare changes

🚀 Enhancements
  • Resolvable configs (#​159)
  • Custom merger to replace built-in defu (#​160)
  • Config update util (#​162)
🩹 Fixes
  • loadConfig: config is not nullable (#​161)
💅 Refactors
  • Internally use named sources (#​158)
🏡 Chore
❤️ Contributors
eslint/eslint (eslint)

v9.5.0

Compare Source

unjs/h3 (h3)

v1.12.0

Compare Source

compare changes

🚀 Enhancements
🩹 Fixes
  • getRequestUrl: Forward opts to getRequestProtocol (#​776)
  • readRawBody: Read chunked body (#​652)
  • proxy: Better error when upstream proxy fails (#​746)
  • node: Make sure onBeforeResponse and onAfterResponse are called with error code (#​756)
  • sse: Prevent onClosed from firing twice in EventStream (#​704)
  • plain: Avoid import from unenv internals (#​781)
💅 Refactors
  • session: Remove unnecessary async for clear (#​729)
  • Update unenv import (76736ea)
📖 Documentation
  • Fix typo (#​699)
  • Fix typo (#​707)
  • Fix typo (#​712)
  • Fix typo (#​730)
  • Fix typo (#​732)
  • Remove extra space (#​718)
  • Add semi (#​710)
  • event-handler: Fix typo (#​684)
  • Add jsdoc examples for response utils (#​677)
  • Add note for getRequestIP return value (#​726)
  • Fix session example (#​702)
  • Add jsdoc examples for request utils (#​680)
  • Fix typo (#​734)
  • Correct zod validation example (#​735)
  • Fix typos (#​738)
  • Fix typo (#​758)
  • Add usage example for handleCors (#​747)
  • Fix typo for text/html content-type (#​764)
  • Update mogen example to use combined log format (#​771)
  • Fix typo for plain adapter example (#​766)
  • examples: Add cors example (#​700)
  • Fix respondWith event object (#​775)
  • Provide async for request body (#​777)
  • error-handling: Add string vs object errors and update createError jsdoc (#​762)
🏡 Chore
🤖 CI
  • Remove node 16 from test matrix (458cfac)
❤️ Contributors
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
pnpm/pnpm (pnpm)

v9.4.0

Compare Source

vuejs/language-tools (vue-tsc)

v2.0.22

Compare Source

Bug Fixes
Other Changes
  • Upgrade Volar from v2.3.0-alpha.14 to v2.3.1.
    • Error tolerant to contentChanges length (#​4457)
  • Add feature request template (#​4490) - Thanks @​so1ve
  • docs: fix wrong links in CHANGELOG.md (#​4475) - Thanks @​KermanX
websockets/ws (ws)

v8.17.1

Compare Source

Bug fixes

A request with a number of headers exceeding the[server.maxHeadersCount][server.maxHeadersCount]
threshold could be used to crash a ws server.

const http = require('http');
const WebSocket = require('ws');

const wss = new WebSocket.Server({ port: 0 }, function () {
  const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split('');
  const headers = {};
  let count = 0;

  for (let i = 0; i < chars.length; i++) {
    if (count === 2000) break;

    for (let j = 0; j < chars.length; j++) {
      const key = chars[i] + chars[j];
      headers[key] = 'x';

      if (++count === 2000) break;
    }
  }

  headers.Connection = 'Upgrade';
  headers.Upgrade = 'websocket';
  headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ==';
  headers['Sec-WebSocket-Version'] = '13';

  const request = http.request({
    headers: headers,
    host: '127.0.0.1',
    port: wss.address().port
  });

  request.end();
});

The vulnerability was reported by Ryan LaPointe in https://github.com/websockets/ws/issues/2230.

In vulnerable versions of ws, the issue can be mitigated in the following ways:

  1. Reduce the maximum allowed length of the request headers using the
    [--max-http-header-size=size][--max-http-header-size=size] and/or the [maxHeaderSize][maxHeaderSize] options so
    that no more headers than the server.maxHeadersCount limit can be sent.
  2. Set server.maxHeadersCount to 0 so that no limit is applied.

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 devdependency c12 to ^1.11.0 chore(deps): update devdependency c12 to ^1.11.1 Jun 12, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 2cedee0 to 29a93a2 Compare June 14, 2024 20:12
@renovate renovate bot changed the title chore(deps): update devdependency c12 to ^1.11.1 chore(deps): update all non-major dependencies Jun 14, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 904b60b to 8d5ea7d Compare June 22, 2024 13:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from cf836e8 to 2166919 Compare June 26, 2024 00:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2166919 to 5886f2b Compare June 26, 2024 09:41
@danielroe danielroe merged commit 31a438a into main Jun 26, 2024
2 checks passed
@danielroe danielroe deleted the renovate/all-minor-patch branch June 26, 2024 10:03
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.

None yet

1 participant