Weekly GitHub Report for Node: June 23, 2025 - June 30, 2025 (23:00:28)
Weekly GitHub Report for Node
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is v23.10.0
1.2 Version Information:
The version released on March 13, 2025, introduces the --experimental-config-file feature, allowing developers to use a JSON configuration file to streamline the use of multiple flags, enhancing the developer experience and potentially increasing adoption. Notable updates include improvements in error handling, updates to root certificates, and the addition of new methods such as tls.getCACertificates() and v8.getCppHeapStatistics(), reflecting a trend towards enhancing security, performance, and developer convenience.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
-
Unable to build node.js in Windows with VS2022: This issue involves a user experiencing difficulties building Node.js version 22.16.0 on a Windows platform using Visual Studio 2022, specifically encountering a compiler issue related to the V8 subsystem. The problem is consistently reproducible, and the user expected a successful build process, but instead encountered errors, prompting them to seek assistance and potential solutions.
- The comments reveal that the issue is specific to Visual Studio 2022 version 17.14, with a suggestion to use ClangCL for future builds starting from Node.js v24. A patch is provided as a temporary workaround, and it is noted that the issue is not urgent since it does not affect CI builds, but a fix is anticipated in future releases.
- Number of comments this week: 6
-
Bug in fileHandle.readableWebStream implementation: This issue reports a bug in the
fileHandle.readableWebStreamimplementation in Node.js version 24.2.0, where an exception is thrown due to an out-of-range error when attempting to read from a stream using a BYOB (Bring Your Own Buffer) reader. The user suggests that the problem lies in the incorrect handling of the byte offset in thenode/lib/internal/fs/promises.jsfile and proposes a fix, although they are unable to test it themselves.- The comments discuss whether the original poster will fix the issue, with suggestions for changes in the code. The original poster clarifies their proposed fix and mentions testing it successfully in their local fork, while another user acknowledges the validity of the proposed solution. The original poster confirms they have created a pull request with their fix.
- Number of comments this week: 5
-
fs.chown crashes when uid is -1: This issue reports a bug in Node.js version 24.3 where the
fs.chownfunction crashes when the user ID (uid) is set to -1, which was not a problem in the previous version 24.2. The crash occurs consistently and is due to an assertion failure in the C++ code that cannot be handled in JavaScript, causing the program to exit immediately.- The comments discuss clarifying the term "crashes," linking a related change that introduced an assertion check for unsigned integers, confirming the issue's presence in version 24.3, and a contributor stating they are working on a fix.
- Number of comments this week: 5
-
Node shows up in macOS 26 developer beta task bar.: This issue pertains to the appearance of Node.js in the taskbar on macOS 26 developer beta, which is affecting all package managers using Node.js due to specific Apple flags that enable verbose mode. The issue is acknowledged as a Node.js problem, and the user has decided to keep the issue open for any potential fixes or solutions.
- Users report that the Node.js taskbar issue causes overheating on MacBook Pro M4, and some suggest using macOS 26 Beta 2, which resolves the taskbar icon issue but not the overheating. There is hope for an Apple fix, and some users consider reverting to macOS Sonoma if the problem persists.
- Number of comments this week: 4
-
Building Node with shared libuv doesn't work with the given
--shared-libuv-path: This issue describes a problem with building Node.js using a shared version of the libuv library, where the specified--shared-libuv-pathis not being used as expected during the compilation process. Instead of using the provided path, the build process defaults to using the libuv library located in/usr/local/lib, which is not the intended behavior according to the user's configuration.- The comments discuss potential reasons for the issue, including the order of linker paths and how the linker might prioritize
/usr/local/libover the specified path. The user confirms that both libraries are similar and questions why the specified path is not prioritized, providing an example of a different project where the desired path order is achieved. - Number of comments this week: 4
- The comments discuss potential reasons for the issue, including the order of linker paths and how the linker might prioritize
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Flaky GC-related tests with V8 12.2: This issue pertains to flaky garbage collection-related tests in the V8 12.2 engine, specifically involving the
test-shadow-realm-gc-module,test-shadow-realm-gc, andtest-net-write-fully-async-hex-stringtests. The problem seems to arise from incorrect assumptions in the tests that are disrupted by V8's new garbage collection strategy, leading to the suggestion of skipping these tests until a more reliable testing method is developed. - Flaky
test-worker-arraybuffer-zerofillwith V8 12.2: This issue concerns a flaky test namedtest-worker-arraybuffer-zerofillassociated with V8 version 12.2, which has been open for over 457 days. The test intermittently fails due to a timeout, suggesting potential underlying bugs or broken timing assumptions, and it has been suggested to mark it as flaky and add logs for further debugging. - Support loading dynamic addon modules (
.nodefiles) when embedding the Node.js shared library without needing to link withnode.def: This issue addresses the challenge of loading dynamic addon modules (.nodefiles) when embedding the Node.js shared library into a different executable without the need to link withnode.def. The proposed solution suggests modifying the delay load hook to utilize an environment variable, potentially namedNODE_LIBRARY, to facilitate the loading process, although the security implications of this approach are still uncertain. - Please make Node.js embeddable (e.g. libnode): This issue is about a request to make Node.js embeddable by creating a
libnodelibrary that would allow Node.js capabilities to be exported and enable N-API access to the host context. The proposal aims to facilitate the integration of Node.js within other environments, such as a Rust-based host process, to allow projects to leverage existing Node.js tooling and dependencies without needing to rewrite code for alternative solutions like Deno. - unable to sign with external OpenSSL engine after usage of crypto.hash: This issue pertains to a problem encountered when attempting to sign with an external OpenSSL engine after using the
crypto.hashfunction in Node.js, specifically affecting versions v21.7.0 and v21.7.1. The error, identified asERR_OSSL_EVP_UNSUPPORTED, arises consistently and is suspected to be linked to recent changes in the Node.js codebase, as the functionality worked correctly in version v21.6.2 and earlier.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 13
Summarized Issues:
- Node.js Build Configuration Issues: The Node.js build process has a problem where the
--shared-libuv-pathoption is ignored, defaulting to the libuv library in/usr/local/lib. This misconfiguration leads to unexpected behavior during the build process, as users expect the specified path to be used.
- Node.js File System Bugs: Several bugs have been identified in the Node.js file system module, including a crash in
fs.chownwhen the user ID is set to -1 and a handle leak inopendirSync()due to an out-of-rangebufferSize. These issues cause unexpected crashes and resource leaks, affecting the stability and reliability of file system operations.
- Node.js Stream and Pipeline Errors: Errors in Node.js streams and pipelines have been reported, such as an unhandled exception in a TypeScript function using
node:stream/promisesand a bug infileHandle.readableWebStreamcausing out-of-range errors. These issues disrupt normal stream operations and lead to test failures and unexpected exceptions.
- Node.js Test Coverage and External Library Issues: Problems with test coverage and external libraries have been noted, including multiple reports generated by
experimental-test-coverageand test failures with an externalized undici library. These issues complicate test result interpretation and integration with external libraries.
- Node.js API and Protocol Schema Concerns: Discussions around Node.js API and protocol schema include the stabilization criteria for NAPI and the absence of the
Network.dataSentevent in thenode_protocol.pdlschema. These concerns highlight the need for clear criteria and complete schema documentation to ensure compatibility and functionality.
- Node.js File System Method Inconsistencies: The
fsPromises.cpmethod has inconsistencies and bugs, such as not accepting Buffer file paths and improper handling of non-UTF8 filenames. These issues necessitate a rework to align its behavior with other methods and improve input validation.
- Node.js Feature Enhancements: Proposed enhancements include adding Float16Array support to node-api version 11 and allowing
v8.writeHeapSnapshotto accept a folder path. These enhancements aim to expand functionality and simplify usage for developers.
- Node.js File System Watcher Bug: A bug in the
fs.watchfunction on Linux causes incorrect rename events for sibling files and directories with similar path prefixes. This issue leads to false positives in file monitoring, affecting applications relying on accurate file system event tracking.
2.4 Closed Issues
This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.
Issues Closed This Week: 13
Summarized Issues:
- Node.js REPL and Asynchronous Evaluation Issues: Node.js version 24.2 has a bug where using the REPL with asynchronous evaluation results in an "ERR_USE_AFTER_CLOSE" error due to the readline instance closing prematurely. This differs from the expected behavior in version 24.1 and earlier, suggesting potential solutions to delay the closing of the readline instance or handle callbacks after closure without causing an error.
- Node.js Test Runner Timeout Issue: The Node.js test runner has a bug where the
run()function ignores the specified timeout option, causing the program to never exit unless the--test-timeoutflag is used. This issue is demonstrated in a provided JavaScript example on a Windows platform.
- Node.js Error Message Spelling Error: There is a spelling error in the error message generated by
WebAssembly.instantiatein Node.js, where "fallthru" should be corrected to "fallthrough" or "fall-through." The error originates from the V8 engine, requiring a fix upstream.
- Node.js
fsAPI Extension Proposal: A proposal has been made to extend thefsAPI to support reading and writing extended file attributes, which can store metadata such as file ID, version, mime type, and checksum. This would involve introducing methods likereadAttributes(),readAttribute(name),writeAttribute(name, value), anddeleteAttribute(name)as part of theFileHandleinterface.
- Node.js
import.meta.mainDiscrepancy: There is a discrepancy in Node.js where theimport.meta.mainproperty behaves inconsistently between JavaScript and TypeScript entry points. Whilemain.jscorrectly printstrue,main.tsincorrectly printsfalse, contrary to the expected behavior as per the Node.js documentation.
- Node.js Proxy and Response Object Bug: In Node.js version 24.2.0, attempting to wrap a
Responseobject in aProxyobject results in aTypeErrordue to the inability to access a private member. This issue does not occur in earlier Node.js versions like 23.0.0 or 23.11.1.
- Node.js Build Issues on Windows: Building Node.js version 24 or above with Link Time Code Generation (ltcg) on Windows fails unless the build is executed within the Visual Studio Developer Command Prompt. This suggests a potential issue with the
vcbuild.batscript not properly setting up the build environment for these versions.
- Node.js Upgrade Linker Error: An attempt to upgrade Node.js from version 23.7.0 to 24.2.0 was halted due to a linker error related to missing symbols for the x86_64 architecture. This is likely caused by an unsupported toolchain configuration using Homebrew's libc++.
- Node.js
require(dir)Exports Field Ignored: Therequire(dir)function in Node.js ignores theexportsfield in thepackage.jsonfile of a directory, defaulting to themainfield instead. This contradicts the expected behavior of prioritizing theexportsfield, as highlighted by the user who questions whether this behavior is intended.
- JavaScript Locale Date Format Discrepancy: There is a discrepancy in the default date format for the 'it-CH' locale in JavaScript's
toLocaleDateString()andIntl.DateTimeFormat(). The default format uses '/' as a date separator instead of the expected '.' according to CLDR standards, and there is also a minor difference in year representation between two and four digits.
- Node.js Error Tracking Mechanism Proposal: A proposal involves implementing a tracking mechanism using npm to leave "crumbs" for error detection. This would allow a system referred to as "the hounds" to track these errors and a "net" to capture them.
- ICU and Currency Symbol Discrepancy: There is a discrepancy in the behavior of ICU between the current and LTS versions of Node.js and the latest browsers regarding the formatting of Ukrainian currency symbols. Node.js correctly uses the textual symbol "грн" for the Ukrainian Hryvnia in the 'uk-UA' locale with
currencyDisplay: 'symbol'as per ICU 77.1+ and CLDR guidelines, while some browsers are outdated and still use the narrow symbol "₴".
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.
III. Pull Requests
3.1 Open Pull Requests
This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Opened This Week: 28
Key Open Pull Requests
1. Add support to print help/usage of util.parseArgs: This pull request introduces functionality to the util.parseArgs module that allows developers to generate and display help text for their command-line interface (CLI) applications, including features such as individual option help text, general help text, automatic help printing via a configuration option, and a method for generating help text, with comprehensive test coverage and documentation updates.
- URL: pull/58875
- Merged: No
2. doc: clarify http.request supports headers as array: This pull request updates the documentation for the http.request() function in the Node.js project to clarify that the headers option can be specified as an array of key-value pairs, similar to the format used in response.writeHead(), and includes additional improvements such as addressing markdown linting issues and ensuring link consistency.
- URL: pull/58810
- Merged: No
3. test_runner: improve mock timer promisifiers: This pull request aims to enhance the mock timer promisifiers in the test runner by adding cleanup logic to remove abort listeners when timers resolve or throw, simplifying the structure of the methods, and converting the #setIntervalPromisified implementation to use a for await loop instead of a custom iterator.
- URL: pull/58824
- Merged: No
Other Open Pull Requests
- File System and Buffer Handling: This topic includes pull requests that address issues related to file system operations and buffer handling in Node.js. One pull request ensures that a directory is closed before an error is thrown when the
options.bufferSizeis invalid. Another fixes the functionality ofFileHandle.readableWebStreamin "byob" mode when reading into a view with abyteOffsetgreater than zero.
- V8 Engine and Async Disposal: These pull requests focus on the V8 engine and async disposal methods in Node.js. One backports a change to expose
disposeandasyncDisposesymbols to the C++ layer, while another makes async disposer methods for HTTP, HTTPS, and HTTP2 servers idempotent.
- Node.js TLS and CA Certificates: A new API,
tls.useSystemCA(), is introduced to allow Node.js TLS clients to use system CA certificates by default. This provides a more secure alternative to existing methods and ensures system certificates are included in the default CA certificate list.
- Node.js Test and Configuration: These pull requests address issues related to testing and configuration in Node.js. One ensures the test runner correctly filters the
--experimental-config-fileoption, while another introduces a--test-files-globflag for custom file pattern matching.
- Node.js Inspector and Debugging: A pull request addresses a crash issue in the Node.js inspector by preventing the propagation of Promise hook events to noPromiseHook. This was causing a debug check failure in async hook inspections during debug builds.
- Node.js Assertion and Error Messages: Enhancements to the Node.js assertion module are proposed to allow printf-style messages and functions as assertion error messages. This aims to optimize performance by reducing the cost of heavy message computations.
- Node.js Deprecation and Resource Management: A pull request proposes the runtime deprecation of closing
fs.Diron garbage collection. This aligns with the upcoming End-of-Life of DEP0137 to encourage explicit resource management.
- Node.js Permission Model and Process Spawning: Changes are introduced to ensure that permission model flags are propagated when using
spawnandspawnSyncmethods. This is similar to how they are already propagated withchild_process.fork.
- Node.js Documentation and Clarity: Pull requests address documentation improvements in Node.js. One adds a missing comma in
child_process.mdfor clarity, while another updates incorrect links intest.md.
- Node.js Metrics and Diagnostics: A new
node:metricsmodule is proposed to introduce a generic metrics capturing interface. This module aims to publishdiagnostics_channelevents, inspired by various ecosystem metrics modules.
- Node.js Release Key Update: The release key for the user "aduh95" in the Node.js project documentation is updated due to the loss of access to the previous key. This necessitated the generation of a new one.
- Node.js Test Synchronization: Tests are introduced to ensure that the content of the
doc/node.1file remains synchronized with thedoc/api/cli.mdfile. This ensures consistency in the documentation of flags and environment variables.
3.2 Closed Pull Requests
This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Closed This Week: 22
Key Closed Pull Requests
1. Fix typo in WebAssembly validation error message (“fallthru” → “fallthrough”): This pull request addresses a minor typo in the WebAssembly validation error message by correcting "fallthru" to "fallthrough" in the source files src/wasm/function-body-decoder-impl.h and src/wasm/function-body-decoder.cc, as well as updating related test expectations, without introducing any behavioral changes, and is linked to issue #58805.
- URL: pull/58819
- Merged: No
- Associated Commits: 33ad8, 51d7c, ea490, f2c74, 0ef27, 48cbd, 5f1e7, 61e7a, fb100, 2d6b1, 5a922, 69302, 93bdd, 5e696, 9af15, 27d36, 37aba, fb601, 9f887, 84424, 68187, 8ba6f, f8362, 73b38, af7c5, f8209, b33ef, 0a991, 8d7d6, fd148, d4069, e4981, d7bfb, d6f9c, d33fc, bda3c, 41646, d5d6e, c5fd1, caec9, f5241, 0b853, 3b41d, 6da44, cef4b, 5bce5, e5521, a6eed, dd1f7, 2449d, 4f192, 72bd2, 8a0b7, 9771f, 8ba30, 07e4a, 5cd3d, a5204, 3d67b, bf0ed, a1dd9, 65618, 2abae, bd3c6, b36fe, c39f1, 2509f, 923a7, ea8e7, 35588, c7238, c2def, cc677, f3e8d, 37953, 34ab1, 48142, 197b6, b3dfc, 5258b, 5f40f, df330, 542aa, 2760d, 4dafd, 22b71, a8670, 8ee20, 049cc, 1a843, cce86, 893b5, 0f690, 7e35a, 7bfb0, c55a3, 6f31c, 09bd3, e3e0c, ee11b, edecd, 7508d, bfd4c, 3ad62, 392a0, 7f3b7, 0a103, 73995, f71a7, e0101, 1b4d2, 0f784, 606c1, e67bc, f3f67, b2a3d, b9bdb, 03e05, 74a17, 93d68, 55a3f, f8ad3, 375c3, e2ea9, e8cb2, 88adb, 17d5b, 5b758, 94970, 1f7a2, 328bd, 64c2c, 0ec4d, ecc18, 1b2af, 18ae7, 8464c, d34fd, 1c1a6, 03005, 2274d, befb9, 8fd81, c6813, 4ad15, 29d20, b4d70, 0a225, a8bc4, 7c349, b42a4, 7e5bb, b05e6, 27491, 6e85b, d116f, c0c60, b6cb7, 4acca, 4ed55, 6fdd7, 9c330, c871f, 6da55, e7d0d, c96f1, 9cf47, 4d051, a4847, acd77, b4946, a1350, 70546, 5df34, 69c21, a905e, 02a83, ca5b8, d7434, bfa49, 5b22f, 235ab, 1d37e, d5a31, 26691, 1e88e, 6af7b, 6826b, 4d5ef, 722fe, 1ec9e, bcc06, 7d1f3, 7e6d9, 20bb1, a9204, c925b, d4f18, 3bcd6, a923a, 5abdd, 0d0ef, ff1f5, b7d80, b965d, 6c5a1, 3dd96, f8e18, 8e7e7, 74328, be587, 26b12, 0c601, 21f1b, d1607, 30482, 70611, ac563, 61f9f, b350f, d9c51, edc3e, 42070, a1817, 981d5, 30154, 760b7, c8305, 69959, c1d3e, 34708, 6cfad, b21a4, 7ba30, bbbfd, f5cd1, b7bc6, 77e2b, e2ae4, 200da, 05328, a5018, e3ad0, 40513, 28d2b, 8c1f8, e6d9f, cffd2, fe0f0, 79760
2. test: deflake test-config-file: This pull request aims to improve the reliability of the "test-config-file" by using a random available port instead of the potentially occupied port 9229 and by saving the configuration file in a temporary directory to allow parallel test execution.
- URL: pull/58799
- Merged: No
3. test_runner: fix timeout not propagated to the child process in run: This pull request addresses an issue where the timeout setting was not being correctly propagated to child processes in the test runner, ensuring that the intended testTimeoutFailure is properly tested and fixing the problem by making the assertion more explicit, as well as resolving an incorrect file path that caused test failures, thereby closing issue #58802 on the Node.js GitHub repository.
- URL: pull/58831
- Merged: Yes
Other Closed Pull Requests
- README.md Updates: This topic involves updates to the README.md file in the Node.js project. The pull request was not merged into the main codebase, indicating potential issues or further revisions needed.
- Test and Error Handling Improvements: Several pull requests focus on improving test consistency and error handling in the Node.js project. These include ensuring directories are properly closed in tests, fixing incorrect error throws in REPL servers, and updating test runners to automatically wait for subtests.
- Documentation Corrections: Multiple pull requests address documentation issues by correcting section orders, adding missing punctuation, and clarifying inheritance descriptions. These changes ensure the documentation is accurate and easier to understand.
- Code Ownership and Permissions: The addition of the @nodejs/inspector team as code owners ensures specific responsibilities and permissions are clearly defined. This change helps streamline code management and accountability within the project.
- Feature Proposals and Enhancements: Proposals for new features include allowing collaborators to block issues and building against a custom
inspector_protocolpath. These proposals aim to enhance project flexibility and align with shared dependencies, though not all were merged.
- Typographical and Punctuation Fixes: Minor corrections include fixing a typo in a WebAssembly error message and adjusting punctuation in test runner error messages. These changes, while small, contribute to the overall quality and professionalism of the codebase.
- Compilation and Inheritance Corrections: Updates to the Node.js project include correcting a compilation error related to mismatched new/delete operations and updating inheritance for
http.OutgoingMessage. These changes ensure proper functionality and adherence to coding standards.
- File System Module Updates: The file system module was updated to standardize error handling by throwing
ERR_INVALID_THISfor invalid contexts. This change replaces previous internal error messages with a more consistent approach.
- Unmerged Proposals and Changes: Some pull requests, such as the creation of a file named "DeviantCrashV6.zip" and a bug fix for the BYOB reader, were not merged. These unmerged changes highlight ongoing discussions or revisions needed before integration.
- Main Branch Merges: A pull request involved merging changes from the main branch, ensuring the project stays up-to-date with the latest contributions and testing guidelines.
3.3 Pull Request Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.
IV. Contributors
4.1 Contributors
Active Contributors:
We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.
If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.
| Contributor | Commits | Pull Requests | Issues | Comments |
|---|---|---|---|---|
| dario-piotrowicz | 28 | 9 | 1 | 37 |
| jasnell | 6 | 2 | 3 | 61 |
| LiviaMedeiros | 14 | 10 | 3 | 9 |
| joyeecheung | 2 | 2 | 1 | 28 |
| legendecas | 8 | 5 | 0 | 10 |
| marco-ippolito | 8 | 2 | 2 | 9 |
| Renegade334 | 7 | 3 | 4 | 4 |
| targos | 4 | 2 | 0 | 12 |
| miguelmarcondesf | 14 | 2 | 0 | 1 |
| IlyasShabi | 3 | 1 | 0 | 13 |