Skip to content

chore(deps): update npm packages - #865

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/npm-packages
Oct 18, 2026
Merged

renovate[bot] merged 1 commit into
mainfrom
renovate/npm-packages

Conversation

@renovate

@renovate renovate Bot commented Oct 18, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@emnapi/runtime 2.0.0-alpha.6 → 2.0.0-beta.2 age adoption passing confidence
@nestjs/common (source) 12.1.2 → 12.1.3 age adoption passing confidence
@nestjs/core (source) 12.1.2 → 12.1.3 age adoption passing confidence
@nestjs/platform-express (source) 12.1.2 → 12.1.3 age adoption passing confidence
@swc/core (source) 1.16.13 → 1.16.18 age adoption passing confidence
emnapi 2.0.0-alpha.6 → 2.0.0-beta.2 age adoption passing confidence
express (source) 5.2.1 → 5.3.0 age adoption passing confidence
file-type 22.1.1 → 22.2.0 age adoption passing confidence
lerna (source) 10.0.1 → 10.1.1 age adoption passing confidence
react (source) 19.3.0 → 19.3.1 age adoption passing confidence
react-dom (source) 19.3.0 → 19.3.1 age adoption passing confidence

Release Notes

toyobayashi/emnapi (@​emnapi/runtime)

v2.0.0-beta.2

Compare Source

What's Changed

Full Changelog: toyobayashi/emnapi@v2.0.0-beta.1...v2.0.0-beta.2

v2.0.0-beta.1

Compare Source

What's Changed

This beta adds experimental support for V8-based WebAssembly addons and introduces addon-neutral names for the core loading APIs.

Highlights
  • Prebuilt V8 static library and NAN support: This release adds a prebuilt libv8 static library for building NAN addons with emnapi’s experimental V8 API shim. The shim supports a subset of the V8 APIs used by NAN. NAN addons that use AsyncWorker or progress workers require threaded builds. (#​236, #​240)
API migration

The core API now uses addon-neutral names so the same loader API can serve N-API, NAN, and V8-based addons. Please migrate to these names:

Deprecated name New name
createNapiModule createAddonModule
loadNapiModule loadAddon
loadNapiModuleSync loadAddonSync
instantiateNapiModule instantiateAddon
instantiateNapiModuleSync instantiateAddonSync
NapiModule AddonModule
MessageHandler.napiModule MessageHandler.addonModule

Instantiation results also use addonModule:

const { addonModule } = await instantiateAddon(wasmInput, options)
const binding = addonModule.exports

The old names remain available as deprecated aliases during the beta. They are scheduled for removal in 2.0.0-rc, so update your code before then. (#​241)

Full Changelog: toyobayashi/emnapi@v2.0.0-alpha.6...v2.0.0-beta.1

nestjs/nest (@​nestjs/common)

v12.1.3

Compare Source

v12.1.3 (2026-10-12)

Bug fixes
Enhancements
  • platform-express, platform-fastify
Docs
Dependencies
Committers: 23
swc-project/swc (@​swc/core)

v1.16.18

Compare Source

Bug Fixes

v1.16.17

Compare Source

Bug Fixes
Features
  • (ci) Restrict pull requests to trusted contributors (#​12463) (ee297d6)

  • (es/codegen) Support configurable output indentation (#​12490) (2058335)

    • BREAKING: support configurable output indentation (#​12490)
Miscellaneous Tasks
Performance
Refactor
  • (es/parser) Isolate parser state and make grammar parameters explicit (#​12425) (5898e8a)
Ci
  • Refresh CodSpeed main baseline (c19d531)
expressjs/express (express)

v5.3.0

Compare Source

=====

🐞 Bug fixes

  • Fixed HTTP header conflict between Content-Length and Transfer-Encoding in res.send - by @​YuryShkoda in #​4893

    Fixed the behavior of res.send() to prevent conflicts between Content-Length and Transfer-Encoding HTTP headers in responses. The Content-Length header in res.send() is now only added when a Transfer-Encoding header is not present, complying with the HTTP specification that states both headers should not coexist in the same response. ETag generation is unaffected by the presence of a Transfer-Encoding header - by @​cuishuang in #​7459

🚀 Improvements

  • Allow conditional revalidation for QUERY requests. req.fresh previously only validated freshness for GET and HEAD requests, so QUERY responses never returned 304 despite a matching validator. Since QUERY is a safe, idempotent, and cacheable method that supports conditional requests, it is now included in the freshness check - by @​Cherry in #​7366

    // QUERY /reports with If-None-Match: "12345"
    app.query('/reports', (req, res) => {
      res.set('ETag', '"12345"');
      res.send(results); // now responds 304 Not Modified
    });
  • Improve HTML structure in res.redirect() responses when HTML format is accepted by adding <!DOCTYPE html>, <title>, and <body> tags for better browser compatibility - by @​Bernice55231 in #​5167

  • When calling app.render with options set to null, the locals object is handled correctly, preventing unexpected errors and making the method behave the same as when options is omitted or an empty object is passed - by AkaHarshit in #​6903

    app.render('index', null, callback); // now works as expected
  • Upgrade content-type to ^2.0.0, bringing a faster parser (~1.5x quicker Content-Type parsing/formatting in res.send()) along with a behavior change: res.send() now keeps any existing parameters when adding the charset and no longer throws on a Content-Type that fails to parse. type-is is upgraded to ^2.1.0 as part of the same change - by @​blakeembrey in #​7234

    res.set('Content-Type', 'text/plain; foo=bar').send('hey');
    // -> Content-Type: text/plain; foo=bar; charset=utf-8
  • The default error handler now logs the full error object instead of only its stack trace, so nested details such as Error.cause and library-specific properties (e.g. Sequelize's parent/original) are no longer swallowed - by @​Nitin-Mohapatra in #​6464

  • Upgrade content-disposition to ^2.0.1, which changes the Content-Disposition header emitted by res.download(), res.attachment(), and res.sendFile(): file names that are valid HTTP tokens are no longer wrapped in quotes. This is equivalent per RFC 6266, but applications asserting on the exact header bytes should update their expectations - by @​blakeembrey in #​7233

    res.attachment('user.html');
    // before -> Content-Disposition: attachment; filename="user.html"
    // after  -> Content-Disposition: attachment; filename=user.html
  • Upgrade body-parser to ^2.3.0, which fixes CVE-2026-12590 (GHSA-v422-hmwv-36x6): an invalid limit option value caused request body size enforcement to be silently disabled (fail-open), allowing a denial of service via arbitrarily large payloads. Invalid limit values now throw at parser initialization instead of being ignored - by @​Mayvis in #​7390

⚡ Performance

  • Avoid duplicate Content-Type header processing in res.send() when sending string responses without an explicit Content-Type header - by @​bjohansebas in #​6991
sindresorhus/file-type (file-type)

v22.2.0

Compare Source


lerna/lerna (lerna)

v10.1.1

Compare Source

Note: Version bump only for package lerna

v10.1.0

Compare Source

Bug Fixes
Features

10.0.1 (2026-08-19)

Bug Fixes
react/react (react)

v19.3.1: 19.3.1 (October 14th, 2026)

Compare Source

React Server Components


Configuration

📅 Schedule: (in timezone Asia/Shanghai)

  • Branch creation
    • "before 10am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot enabled auto-merge (squash) October 18, 2026 18:34
@renovate
renovate Bot merged commit 513cdee into main Oct 18, 2026
26 of 27 checks passed
@renovate
renovate Bot deleted the renovate/npm-packages branch October 18, 2026 18:37
Brooooooklyn added a commit that referenced this pull request Oct 19, 2026
@emnapi/core 2.0.0-beta.2 breaks @napi-rs/wasm-runtime 1.2.5, the
latest: loading the WASI binding fails with "Cannot set properties of
undefined (setting 'initWorker')". Go back to the versions main used
before #865, where the wasm build and the WASI tests passed, and pin
them so a range cannot move one of them alone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Brooooooklyn added a commit that referenced this pull request Oct 19, 2026
@emnapi/core 2.0.0-beta.2 breaks @napi-rs/wasm-runtime 1.2.5, the
latest: loading the WASI binding fails with "Cannot set properties of
undefined (setting 'initWorker')", and #865 moving only emnapi and
@emnapi/runtime to beta.2 fails the wasm build. Pin all three to
2.0.0-alpha.6, so a range cannot move one of them alone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Brooooooklyn added a commit that referenced this pull request Oct 19, 2026
@emnapi/core 2.0.0-beta.2 breaks @napi-rs/wasm-runtime 1.2.5, the
latest: loading the WASI binding fails with "Cannot set properties of
undefined (setting 'initWorker')", and #865 moving only emnapi and
@emnapi/runtime to beta.2 fails the wasm build. Pin all three to
2.0.0-alpha.6, so a range cannot move one of them alone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Brooooooklyn added a commit that referenced this pull request Oct 19, 2026
@emnapi/core 2.0.0-beta.2 breaks @napi-rs/wasm-runtime 1.2.5, the
latest: loading the WASI binding fails with "Cannot set properties of
undefined (setting 'initWorker')", and #865 moving only emnapi and
@emnapi/runtime to beta.2 fails the wasm build. Pin all three to
2.0.0-alpha.6, so a range cannot move one of them alone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Brooooooklyn added a commit that referenced this pull request Oct 19, 2026
@emnapi/core 2.0.0-beta.2 breaks @napi-rs/wasm-runtime 1.2.5, the
latest: loading the WASI binding fails with "Cannot set properties of
undefined (setting 'initWorker')", and #865 moving only emnapi and
@emnapi/runtime to beta.2 fails the wasm build. Pin all three to
2.0.0-alpha.6, so a range cannot move one of them alone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Brooooooklyn added a commit that referenced this pull request Oct 19, 2026
#865 moved emnapi and @emnapi/runtime to 2.0.0-beta.2 but left
@emnapi/core at 2.0.0-alpha.6, and @napi-rs/cli refuses the mismatch,
so the wasm32-wasip1-threads build fails. Moving all three to beta.2
is not the fix: @emnapi/core beta.2 breaks @napi-rs/wasm-runtime 1.2.5,
the latest ("Cannot set properties of undefined (setting
'initWorker')"). Pin all three to 2.0.0-alpha.6, as before #865, so a
range cannot move one of them alone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Brooooooklyn added a commit that referenced this pull request Oct 20, 2026
Bottom of stack #867: #861 and #863 build on it, so their CI gets
working emnapi versions.

#865 on main moved `emnapi` and `@emnapi/runtime` to `2.0.0-beta.2` but
left `@emnapi/core` at `2.0.0-alpha.6`. `@napi-rs/cli` refuses the
mismatch, so `stable - wasm32-wasip1-threads - node@24` fails on main,
and the 5 test jobs after it are skipped:

```
Internal Error: emnapi version mismatch: emnapi@2.0.0-beta.2, @emnapi/core@2.0.0-alpha.6, @emnapi/runtime@2.0.0-beta.2.
```

Moving all three to beta.2 is not the fix: `@emnapi/core` beta.2 breaks
`@napi-rs/wasm-runtime` 1.2.5, the latest, and `Test WASI target` fails
to load the binding (`Cannot set properties of undefined (setting
'initWorker')`).

So this pins all three to exactly `2.0.0-alpha.6`, the versions main
used before #865 (where both wasm jobs passed). Move them together once
`@napi-rs/wasm-runtime` supports emnapi beta.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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