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
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

The current version of this repository is v23.10.0

1.2 Version Information:

Released on March 13, 2025, this version introduces the --experimental-config-file feature, allowing developers to use JSON configuration files to simplify flag management for test runners and other features, enhancing developer experience. Additionally, it includes updates to root certificates, new TLS and V8 methods, improved error handling, and various tooling and documentation enhancements.

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.

As of our latest update, there are no active issues with ongoing comments this week.

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.

As of our latest update, there are no stale issues for the project this week.

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: 0

Summarized Issues:

As of our latest update, there are no open issues for the project this week.

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: 4

Summarized Issues:

• Function input validation errors: The util.styleText() function in Node.js versions 25.7.0 and later no longer accepts format aliases such as "grey," causing it to throw a TypeError, whereas previous versions accepted these aliases as valid inputs. This change breaks backward compatibility and requires users to update their code to avoid errors.
• issues/62177

• CI workflow failures: The lint-nix GitHub Action intermittently hangs and silently fails during CI runs, causing timeouts without clear failure indicators. A temporary workaround involves switching the runner to ubuntu-latest to avoid these silent failures.
• issues/62219

• Architecture-specific memory corruption: Node.js v24.14.0 crashes consistently on aarch64 Linux due to heap memory corruption or double free errors, likely caused by a bug in the ARM64 build's memory allocator or related runtime components. This results in process aborts across multiple projects and suggests allocator or alignment problems specific to this architecture.
• issues/62253

• Incorrect lambda capture causing dangling references: A bug in DatabaseSync::ApplyChangeset() within node_sqlite.cc involves a lambda incorrectly capturing filterFunc by reference, leading to a dangling reference because filterFunc goes out of scope before the callback is invoked. The issue suggests capturing filterFunc by value to fix the problem.
• issues/62276

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: 0

As of our latest update, there are no open pull requests for the project this week.

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: 17

Key Closed Pull Requests

1. tools: fix timeout errors in lint-nix job: This pull request addresses and fixes timeout errors occurring in the lint-nix job within the project's tooling, resolving the related issue reported in the Node.js repository.

• URL: pull/62265

• Associated Commits: cbae6, 1607b, f51d1, f6ca2

• Associated Commits: cbae6, 1607b, f51d1, f6ca2

2. stream: preserve error over AbortError in pipeline: This pull request fixes an issue in the Node.js stream pipeline where errors thrown inside Readable.map() were being swallowed and replaced by an AbortError, by ensuring that user errors take precedence over internal cleanup AbortErrors during stream destruction and error propagation.

• URL: pull/62113

• Associated Commits: a5811, 0dc1e, 543ce

• Associated Commits: a5811, 0dc1e, 543ce

3. doc: test and test-only targets do not run linter anymore: This pull request updates the documentation and inline comments to accurately reflect that the make test and make test-only targets no longer run linters, addressing the issue reported in https://github.com/nodejs/node/issues/58606.

• URL: pull/62120

• Associated Commits: 73a7a, 4cb68

• Associated Commits: 73a7a, 4cb68

Other Closed Pull Requests

• TestContext subtest variants fix: This pull request addresses a bug in the Node.js test runner by adding the skip, todo, only, and expectFailure variant methods to the TestContext's test() method for subtests, ensuring parity with the top-level test() function and preventing TypeError when these variants are called within subtests. This improves the consistency and usability of subtests in the testing framework.
  pull/62156

• util.styleText color alias fix: This pull request fixes an issue where the util.styleText() function would throw an error for valid color aliases like 'grey' by changing the method to use ObjectGetOwnPropertyNames instead of ObjectKeys to correctly fetch both keys and aliases. Additional tests were included to verify this corrected behavior.
  pull/62180

• fs.ReadStream and fs.WriteStream documentation update: This pull request clarifies in the documentation that fs.ReadStream and fs.WriteStream should not be constructed directly using the new keyword, aligning with the existing pattern for fs.Stats. It emphasizes that the supported way to create these streams is through the factory functions fs.createReadStream() and fs.createWriteStream().
  pull/62208

• child_process.spawn() Windows shell example removal: This pull request removes the deprecated example recommending the use of child_process.spawn() with the shell option for running .bat and .cmd files on Windows from the documentation. This addresses shell injection risks and continues previous efforts to update guidance by promoting safer alternatives like exec() and direct cmd.exe spawning.
  pull/62243

• Native C++ API for OpenSSL SSL_CTX access: This pull request introduces a new native C++ API, crypto::GetSSLCtx, to provide addons with direct and official access to OpenSSL SSL_CTX contexts. It replaces the previously used but unsupported _external field in the JavaScript API, improving encapsulation and stability for native addon integration with Node's OpenSSL implementation.
  pull/62254

• Renaming length to outputLength in crypto params: This pull request renames the length property to outputLength in the CShakeParams and KmacParams dictionaries to align their implementation with a recent change in the webcrypto-modern-algos project. This ensures consistency and maintains dictionary attribute order.
  pull/61875

• ESM loader path normalization fix: This pull request fixes the path normalization logic in the finalizeResolution function within the ECMAScript module (ESM) loader of the Node.js project. The fix addresses issues identified in a previous related pull request.
  pull/62080

• Benchmark config key rename and iteration count update: This pull request fixes a destructuring bug in the dgram/single-buffer benchmark caused by a config key rename from num to n. It also updates the iteration count parameter in three crypto benchmark files to use the standard n convention for consistency.
  pull/62084

• Coverage report fix for mocked CommonJS modules in ESM: This pull request fixes the issue where mocked CommonJS modules imported from ESM modules incorrectly appear with partial coverage in the coverage report. It ensures that the full URL, including the ?node-test-mock search parameter, is passed to the V8 compiler function to correctly identify mocked modules during coverage analysis.
  pull/62133

• Stream module deprecation warning promotion: This pull request promotes the deprecation warning DEP0201 in the stream module to a runtime deprecation. This indicates that the feature is now officially deprecated during execution.
  pull/62173

• Backport TLS module refactors to v22.x: This pull request backports the refactors of the _tls_common and _tls_wrap modules to the v22.x branch. It replicates the original changes while omitting the process.emitWarning calls and related unit tests for deprecation warnings.
  pull/62231

• AIX 7.3 test hang workaround: This pull request implements a workaround by skipping the test-cluster-dgram-reuse test on AIX 7.3 to prevent a reproducible hang during testing on that platform. This enables AIX 7.3 to be included in continuous integration without affecting coverage on AIX 7.2.
  pull/62238

• --eval option syntax clarification and tests: This pull request clarifies the syntax for using the --eval option with scripts that start with a leading hyphen by documenting the --eval=<script> form as a workaround. It also adds tests for cases like --eval=-42, --eval=-0, and the -e -p missing-argument error.
  pull/62244

• Performance improvement in IndexOfString function: This pull request replaces heap allocations with stack allocations using MaybeStackBuffer in the Latin1 path of the IndexOfString function. This results in a 12-15% performance improvement for short string searches by avoiding malloc and free calls.
  pull/62268

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.