Repository navigation
chore(deps): update npm packages - #865
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.0.0-alpha.6→2.0.0-beta.212.1.2→12.1.312.1.2→12.1.312.1.2→12.1.31.16.13→1.16.182.0.0-alpha.6→2.0.0-beta.25.2.1→5.3.022.1.1→22.2.010.0.1→10.1.119.3.0→19.3.119.3.0→19.3.1Release Notes
toyobayashi/emnapi (@emnapi/runtime)
v2.0.0-beta.2Compare Source
What's Changed
Full Changelog: toyobayashi/emnapi@v2.0.0-beta.1...v2.0.0-beta.2
v2.0.0-beta.1Compare 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
libv8static 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 useAsyncWorkeror 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:
createNapiModulecreateAddonModuleloadNapiModuleloadAddonloadNapiModuleSyncloadAddonSyncinstantiateNapiModuleinstantiateAddoninstantiateNapiModuleSyncinstantiateAddonSyncNapiModuleAddonModuleMessageHandler.napiModuleMessageHandler.addonModuleInstantiation results also use
addonModule: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.3Compare Source
v12.1.3 (2026-10-12)
Bug fixes
core,microservicesplatform-expressStreamableFilesource on client disconnect (@maxymlyskov)coreGETmiddleware exclusion coverHEADrequests (@Chaoqi31)Map,SetandRegExpoptions in deep-hash tokens (@Chaoqi31)VERSION_NEUTRALin middleware routes as no version (@Chaoqi31)x-powered-byinuseSecurityHeaders()(@Chaoqi31)microservicesplatform-fastifyreturn503OnClosingduring the shutdown hooks (@thekhegay)useBodyParser()(@Chaoqi31)reply.rawinisHeadersSent(@Chaoqi31)common@Inject()property replace the parent's (@Chaoqi31)@Optional()properties optional (@Chaoqi31)microservices,websocketswebsocketscommon,core,platform-expressplatform-wscore,websocketscore,testinguseClass()overrides (@Chaoqi31)Enhancements
platform-express,platform-fastifyDocs
Dependencies
platform-fastifyplatform-socket.ioCommitters: 23
swc-project/swc (@swc/core)
v1.16.18Compare Source
Bug Fixes
(bindings) Fall back to a safe cache root on Unix (#12500) (2125403)
(es/minifier) Check decl for side effect (#12501) (6841927)
v1.16.17Compare Source
Bug Fixes
(bindings) Fall back to a secure Windows profile cache (#12452) (2c0fb89)
(bindings) Allow opting out of Unix cache root security checks (#12469) (e87fa40)
(ci) Run main CodSpeed benchmarks after policy skips (1b6d869)
(ci) Match Rust's z10 baseline in s390x release builds (#12489) (b96f92f)
(ci) Raise native addon MSRV to Rust 1.85 (#12491) (54a2324)
(ci) Repair empty crate release changeset (#12499) (6bf5f8c)
(cli) Resolve out-dir source map paths relative to output (#12481) (717914f)
(deps) Update cargo (#10278) (fc7a9e2)
(es/compat) Preserve consecutive loop labels (#12472) (28c3370)
(es/estree) Fix AST roundtrip bugs and implement missing conversions (#12440) (898b592)
(es/fixer) Preserve parentheses in JSX sequence expressions (#12485) (7a36735)
(es/preset-env) Lower for-await in native async functions (#12414) (2b3d306)
(react-compiler) Protect long call chains from stack overflow (#12473) (a19b101)
Direct unapproved contributors to open issues (#12479) (3fac5ec)
Features
(ci) Restrict pull requests to trusted contributors (#12463) (ee297d6)
(es/codegen) Support configurable output indentation (#12490) (2058335)
Miscellaneous Tasks
(deps) Replace dependency babel-eslint with @babel/eslint-parser ^7.11.0 (#12456) (a933f98)
(deps) Replace dependency npm-run-all with npm-run-all2 ^5.0.0 (#12457) (98e6c6e)
(deps) Update npm (#12468) (7c75e36)
Performance
(es/compat) Skip empty block-scoping renames (#12478) (952db74)
(es/parser) Scan template literals with byte search (#12474) (3c46139)
Refactor
Ci
expressjs/express (express)
v5.3.0Compare 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 betweenContent-LengthandTransfer-EncodingHTTP headers in responses. TheContent-Lengthheader inres.send()is now only added when aTransfer-Encodingheader 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 aTransfer-Encodingheader - by @cuishuang in #7459Upgrade
qsto^6.16.0, which fixes CVE-2026-2391 (GHSA-w7fw-mjwx-w883), CVE-2026-82417 (GHSA-4mjr-xmp4-gh2g) and CVE-2026-82562 (GHSA-x5fp-wj9c-mxmx):arrayLimitbypasses in comma parsing and a denial of service via an attacker-controlledisBuffer- by @davetashner in #7057 and #7478, and @cyphercodes in #7305Upgrade
proxy-addrto^2.0.8, which fixes CVE-2026-90711 - by @lazerg in #7474🚀 Improvements
Allow conditional revalidation for QUERY requests.
req.freshpreviously 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 #7366Improve 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 #5167When calling
app.renderwith 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 #6903Upgrade
content-typeto^2.0.0, bringing a faster parser (~1.5x quickerContent-Typeparsing/formatting inres.send()) along with a behavior change:res.send()now keeps any existing parameters when adding the charset and no longer throws on aContent-Typethat fails to parse.type-isis upgraded to^2.1.0as part of the same change - by @blakeembrey in #7234The default error handler now logs the full error object instead of only its stack trace, so nested details such as
Error.causeand library-specific properties (e.g. Sequelize'sparent/original) are no longer swallowed - by @Nitin-Mohapatra in #6464Upgrade
content-dispositionto^2.0.1, which changes theContent-Dispositionheader emitted byres.download(),res.attachment(), andres.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 #7233Upgrade
body-parserto^2.3.0, which fixes CVE-2026-12590 (GHSA-v422-hmwv-36x6): an invalidlimitoption value caused request body size enforcement to be silently disabled (fail-open), allowing a denial of service via arbitrarily large payloads. Invalidlimitvalues now throw at parser initialization instead of being ignored - by @Mayvis in #7390⚡ Performance
res.send()when sending string responses without an explicit Content-Type header - by @bjohansebas in #6991sindresorhus/file-type (file-type)
v22.2.0Compare Source
bde605ae49d5b77702ad16a9ab987ce44a5a2e758alerna/lerna (lerna)
v10.1.1Compare Source
Note: Version bump only for package lerna
v10.1.0Compare 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)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.