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 like node.config.json to simplify flag management for test runners and other experimental 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.

1. [BUFFER] Regression in Node.js 26.8.0: aligned Buffer pool breaks multi-byte typed-array views: This issue reports a regression introduced in Node.js versions 26.8.0 and 26.8.1 where the aligned Buffer pool causes multi-byte typed-array views to throw a RangeError due to the backing ArrayBuffer length increasing from 65,536 to 65,599 bytes. This change breaks code that previously worked in Node.js 26.7.0 by causing typed-array constructors without explicit lengths to fail when the element size does not divide the larger backing buffer size evenly.

   • The comments discuss whether this behavior constitutes unsafe usage or a bug, with some users arguing the original code was safe and others noting the unusual backing buffer size; it is clarified that the buffer alignment to cache lines causes the size increase, which brings minor performance benefits, and the issue is recognized as a regression worth investigating.
   • Number of comments this week: 6

2. [VM] [LOADERS] vm: SourceTextModule memory leak - instances retained via async context frames after evaluate(): This issue reports a memory leak in Node.js's vm module where instances of SourceTextModule are retained via async context frames after calling evaluate(), causing heap memory to grow by about 80 MB per iteration without shrinking despite garbage collection. The root cause is traced to the microtask queue holding async context frames with error stack traces that reference the module, preventing the vm.Context and SourceTextModule from being collected even after all JS references go out of scope.

   • The comments discuss that the observed memory growth is due to lazy garbage collection rather than a true leak, showing that forcing a heap snapshot triggers GC that reclaims memory; suggestions include using more aggressive GC flags and addressing the compilation cache that holds module exports alive, with ongoing investigation into potential solutions such as adding user options to disable the compilation cache or making ESM bytecode ageable, and a tentative upstream change is linked.
   • Number of comments this week: 3

3. [DOC] [DISCUSS] Proposal: Remove ESM/CJS duality from code samples in API docs: This issue proposes removing the duality of ESM and CJS code samples in the API documentation by consolidating them into a single JavaScript code block that uses ESM imports as the standard, except where CJS-specific examples are necessary. The goal is to reduce duplicated code blocks and improve the clarity and maintainability of the documentation by avoiding redundant togglable examples that differ only in import syntax.

   • The comments include a request to work on the issue, a clarification that this is a policy proposal rather than a bug with guidance on contributing, and a note about the potential removal of CJS examples from contributing documentation as part of ongoing efforts to reduce reliance on CJS code samples.
   • Number of comments this week: 3

4. node:test Tests without callback should not be reported as ok: This issue addresses the problem where tests defined without a callback function are incorrectly reported as passing, which can mislead developers into thinking unimplemented tests have succeeded. The reporter suggests that such tests should instead be marked as TODO or pending, aligning with behaviors in other testing frameworks like Mocha and Vitest, to avoid giving a false sense of test coverage.

   • The comments include a disagreement on whether this is a bug, a detailed explanation of why the current behavior is problematic from a QA perspective, and confirmation that other testing frameworks mark such tests as pending or todo, supporting the reporter’s viewpoint.
   • Number of comments this week: 3

5. [BUILD] configure does not support Python 3.15: This issue reports that the Node.js configure script does not currently support Python 3.15, even though the user believes Python 3.15 release candidate should work fine for compiling Node.js. The user requests consideration for adding support for Python 3.15 in the configure step to avoid downgrading Python versions during compilation.

   • The comments suggest manually modifying the configure script to accept Python 3.15 at the user's own risk, note that official support typically follows closer to the final Python release date, and recommend downgrading to a supported Python version until thorough testing of Python 3.15 is completed across all environments.
   • Number of comments this week: 3

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

Summarized Issues:

• Incorrect Object String Tags: The Object.prototype.toString method returns incorrect string tags for MessageChannel and MessagePort objects, showing [object Object] and [object EventTarget] instead of the expected tags. This is due to missing or inherited Symbol.toStringTag properties on their prototypes, causing misleading object identification.
  • issues/65527

• Error Handling in Network Methods: The setKeepAlive() method in the net subsystem ignores errors from the underlying handle and always returns the socket object, failing to indicate failure. This contrasts with similar methods that properly propagate such errors, leading to silent failures in keep-alive settings.
  • issues/65529

• Documentation Simplification: There is a proposal to remove dual ESM/CJS code examples in the API documentation in favor of a single canonical ESM import style. This aims to reduce duplicated code blocks and simplify maintenance of the documentation.
  • issues/65536

• Shared Microtask Queues Proposal: A proposal suggests adding support for shared microtask queues across multiple VM contexts to align with the HTML Standard's event loop model. This would enable precise control over microtask draining order in scenarios like Window and iframe realms sharing an event loop.
  • issues/65555

• Test Coverage Reporting Bug: Tests written without a callback function are incorrectly marked as passing, giving a false impression of test coverage. Such tests do not execute assertions and should be reported as incomplete or todo instead.
  • issues/65563

• TLS CRL Loading Bug: The TLS implementation only loads the first Certificate Revocation List (CRL) from a concatenated PEM bundle, ignoring subsequent CRLs. This causes certificate verification failures when multiple CRLs are present because the intended loop processing is not performed.
  • issues/65576

• Mutual-TLS Certificate Chain Regression: In Node.js v26.8.0, socket.getPeerCertificate(true) no longer returns the full client certificate chain during mutual-TLS connections. Instead, issuer certificates are dropped due to a caching interaction triggered by internal use of getPeerX509Certificate() in the TLS handshake.
  • issues/65579

• REPL Infinite Loop Bug: Typing Promise.any([]). in the REPL causes an infinite loop that spams messages and can make the REPL unresponsive. This happens because the completer evaluates the expression and repeatedly triggers unhandled promise rejections.
  • issues/65581

• Collaborator Nomination: Guilherme (@araujogui) is proposed as a collaborator for the Node.js project due to significant contributions, active community involvement, and demonstrated commitment.
  • issues/65585

• Sqlite Segmentation Fault Bug: User-supplied JavaScript getters run mid-call during option retrieval in the sqlite subsystem, causing stale state usage. This leads to a segmentation fault instead of the expected error handling.
  • issues/65586

• Python 3.15 Support Missing: The Node.js configure script does not support Python 3.15, preventing compilation with this version. The reporter believes Python 3.15 should work fine for building Node.js.
  • issues/65599

• Memory Leak in zlib APIs: A memory leak regression in Node.js v24.15.0 causes arrayBuffers to accumulate without garbage collection during repeated calls to one-shot zlib gzip()/deflate() APIs. This leads to out-of-memory errors in long-running processes despite memory being reclaimable with forced GC.
  • issues/65600

• Buffer Pool Regression: Node.js 26.8.0 introduced a regression where the aligned Buffer pool causes multi-byte typed-array views to throw a RangeError. This happens because the backing ArrayBuffer's byte length is no longer a multiple of the typed-array element size, breaking behavior that worked in 26.7.0.
  • issues/65601

• Proxy Bypass Inconsistency: The NO_PROXY environment variable does not cause http.request() to bypass proxies for subdomains, unlike fetch(). This leads to inconsistent proxy behavior between these two methods when using values like example.com.
  • issues/65616

• Abort Listener Bug: Disposing an addAbortListener does not prevent it from being called if the signal is already aborted, and the listener is invoked with an undefined event argument instead of a proper Event object. This causes unexpected behavior and errors.
  • issues/65637

• Child Process Close Event Suppression: In Node.js versions 22, 24, and 26, calling child_process's parent disconnect() suppresses the child's close event after exit. This causes incomplete event accounting and potential cleanup timeouts despite proper termination of the child process and its resources.
  • issues/65646

• Test Runner Assertion Failure: The Node.js test runner aborts with an assertion failure in InternalCallbackScope::Close when a bind(2) system call returns EPERM during server.listen(). Instead of reporting the listen error properly, the process exits unexpectedly under certain Linux conditions.
  • issues/65667

• HTTP/2 Stream Async Iteration Regression: In Node.js v26.3.0+ and v24.20.0, asynchronous iteration over HTTP/2 streams prematurely reports a stream close error despite buffered and readable response bodies. This causes ERR_STREAM_PREMATURE_CLOSE to be thrown during consumption of complete responses.
  • issues/65677

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

Summarized Issues:

• Async Hooks and Event Loop Behavior: Issues with async_hooks.triggerAsyncId() not returning expected async IDs due to callback context discrepancies and SIGTERM handlers failing to execute when no active tasks keep the event loop alive cause unexpected process behavior and termination. These problems highlight inconsistencies between documented and actual event loop and async hook behaviors in Node.js.
• [issues/21078, issues/28502]

• Cryptography Cipher Recognition and Support: Node.js fails to recognize certain authenticated ciphers like AES-256-CBC-HMAC-SHA256 and SM4-GCM/CCM modes due to OpenSSL 3 changes and build configurations, resulting in errors and missing runtime support despite documentation and OpenSSL inclusion. This leads to broken or incomplete cryptographic functionality in affected Node.js versions.
• [issues/43040, issues/64866]

• Buffer and Stream API Documentation and Behavior: Undocumented Buffer methods raise questions about public API status, and the Child Process API documentation incorrectly describes stream directions for stdio options, causing confusion and potential misuse. These documentation issues require clarification to align user expectations with actual API behavior.
• [issues/46467, issues/56623]

• Network and Protocol Test Failures and Crashes: Tests involving UDP IPv6 link-local addresses and QUIC stream stop-sending states fail due to interface scoping and timing issues, while HTTP/3 QUIC sessions cause segmentation faults on process exit, indicating instability and flaky behavior in network protocol implementations and tests.
• [issues/46792, issues/63309, issues/65408]

• Event Listener Management Bugs: EventTarget's removeEventListener method fails to remove all matching listeners, and abort signal listeners added with {signal} can be garbage collected prematurely, causing lingering or improperly removed event listeners and unexpected event handling behavior.
• [issues/63954, issues/65244]

• File and Stream Handling Bugs: The ZipFile.close() method hangs indefinitely when pausing file-backed content iterators, and fused stateless stream transforms fail to normalize output properly, leading to hangs and incorrect data processing in file and stream operations.
• [issues/65277, issues/65366]

• Native Module and Memory Safety Crashes: ffi subsystem crashes with segmentation faults on invalid DynamicLibrary getter calls, and SQLite exhibits use-after-free vulnerabilities and crashes due to premature garbage collection and reentrancy guard gaps, causing process instability and security risks.
• [issues/65287, issues/65428, issues/65447, issues/65460]

• Documentation Discrepancies and Error Handling Issues: The default value for server.maxHeadersCount is incorrectly documented, and fs.openAsBlob throws generic errors instead of specific system errors, leading to confusion and difficulty in debugging due to inaccurate or incomplete error reporting.
• [issues/65470, issues/65514]

• Build and Versioning Problems: Node.js macOS binaries are built with outdated Xcode causing UI issues, version 26.8.0 releases incorrectly show alpha version strings, and builds fail on macOS arm64 due to missing standard library components, reflecting problems in build environments and release processes.
• [issues/62984, issues/65566, issues/65620]

• File System Operation Failures on Windows: On Windows with Node.js v24, fs.rm and fs.rmSync silently fail to delete files with non-ASCII characters, and fs.promises.rm crashes with a TypeError, indicating regressions in file system operations involving Unicode paths.
• [issues/65578]

• Large Memory Allocation and User Requests: Creating very large arrays causes fatal errors due to V8's internal memory allocation limits, and user requests to upgrade Node.js versions for mobile deployment are closed as out of scope, showing limitations in resource handling and project scope boundaries.
• [issues/65534, issues/65525]

• Test Documentation Enhancement Proposal: A proposal to add a diagram illustrating the lifecycle of test reporter events aims to improve understanding of event sequences and triggers during test execution, enhancing documentation clarity.
• [issues/51908]

• Unspecified or Reference-Only Issue: An issue referencing another for details without providing specific information itself, indicating a placeholder or meta-report.
• [issues/65668]

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

Key Open Pull Requests

1. stream: second batch of stream/iter fixes: This pull request builds upon a previous stream/iterator-related update and introduces a second batch of fixes aimed at improving cancellation handling, iterator cleanup, write termination, metadata stability, re-entrancy defense, full-close semantics, error tracking, synchronous close requirements, and various other stream and iterator behaviors to enhance robustness and correctness in the Node.js stream implementation.

• URL: pull/65658

• Associated Commits: 59b83, 9720f, 03564, 9647d, a35ae, 6141f, 7db52, 91102, c4693, 21f0f, 06d16, 9b364, 5f252, 0df59, d95bc, eea6e, 432df, e6b2c, 90176, b80ae, 39c9d, f4ffb, 464d5

2. bench: additional work on node:bench: This pull request is a comprehensive follow-up to a previous PR that continues the implementation and enhancement of the node:bench benchmarking module in Node.js, including new APIs, improved test coverage, diagnostic support, documentation clarifications, and various fixes, while remaining in draft until the initial PR is merged.

• URL: pull/65631

• Associated Commits: 2dbf8, de895, 3470d, 39d68, 2e11e, 3189d, eb454, 7ff10, 8818a, 69ca5, 5fef3, 29f48, 7145f, 685da, 81c8b, d7d20, ca083, 640f1, 7a12e, b5e9f, 109cf, 3163d

3. crypto: add FIPS indicator diagnostics and strict mode: This pull request introduces a FIPS indicator diagnostics channel and a strict enforcement mode to Node.js's crypto module, enabling visibility into non-FIPS-approved operations permitted by OpenSSL FIPS providers and allowing users to opt into runtime enforcement of strict FIPS compliance via new flags such as --enable-fips-indicator-events and enhanced --force-fips modes without impacting existing defaults or performance.

• URL: pull/65645

• Associated Commits: debb4, 38263, 077a0, 4883a, e3ba1, 8a05f, b83f3

Other Open Pull Requests

• Crypto module enhancements: Multiple pull requests improve cryptographic functionality by introducing crypto.parsePKCS12() to parse PKCS#12 bundles directly in JavaScript, caching valid ECDH key pairs to avoid redundant validation, and improving startup performance by lazy loading cryptographic ciphers and removing costly atexit() handlers. These changes enhance both usability and performance of cryptographic operations in Node.js.
  • pull/65627, pull/65615, pull/65549

• QUIC and stream improvements: The QUIC implementation was refactored to reuse the TLS handshake suspension mechanism, simplifying 0RTT handling and improving handshake clarity. Additionally, new drain() and drainSync() methods were added to the node:stream/iter module to efficiently consume and discard streams, improving memory usage especially in QUIC stream scenarios.
  • pull/65522, pull/65598

• TypeScript typings for internal bindings: TypeScript typings were added for the internal fs_event_wrap and task_queue bindings, including new declaration files, integration into the InternalBindingMap, and typed definitions for classes, methods, and events. This improves type safety and developer experience when working with these internal Node.js components.
  • pull/65661, pull/65662

• SQLite integration fixes and improvements: Several pull requests address stability and safety in the SQLite integration by validating that the database connection remains open after reading options, re-validating database state to prevent crashes from user-supplied property getters, adding buffer length and callback arity checks, and including regression tests. These changes prevent segmentation faults and ensure data integrity.
  • pull/65591, pull/65595

• Virtual file system (VFS) support: New features enable mounting bundled assets as a read-only virtual file system with the "useVfs" option, allowing main scripts and dependencies to run from within this mount with proper resolution. Native addons can also be loaded directly from the VFS by reading bytes and loading them through a platform-specific self-cleaning image, maintaining compatibility without changing existing interfaces.
  • pull/65675, pull/65680

• Object inspection improvements: The Symbol.toStringTag property was added to the prototypes of MessageChannel, MessagePort, and BroadcastChannel classes to ensure Object.prototype.toString.call() returns their correct interface names. This fixes object inspection outputs and related test expectations, aligning with HTML and WebIDL specifications.
  • pull/65532, [pull/65531](https://github.com/pull/65531]

• Filesystem and I/O fixes and performance: Fixes include coercing non-number length arguments in fs.promises.FileHandle.read() to integers to prevent aborts, resolving recursive cpSync EACCES errors on Docker VirtioFS by switching to libuv's copy method, and improving recursive directory reading performance by reducing C++/JS round-trips and optimizing file status checks. These changes enhance robustness and speed of filesystem operations.
  • pull/65521, pull/65520, pull/65547

• TLS and network improvements: The TLS implementation was fixed to correctly load all Certificate Revocation Lists from PEM bundles by reading until the BIO is exhausted, preventing errors like UNABLE_TO_GET_CRL. Additionally, Socket.prototype.setKeepAlive() was fixed to throw on non-zero error codes (except Windows), aligning behavior with setTypeOfService(), and a warning was added for truncated keep-alive delay values below 1000ms.
  • pull/65577, pull/65539, [pull/65528](https://github.com/pull/65528]

• Performance and memory optimizations: Webstream state management was optimized by replacing dictionary-mode objects with fast-mode class instances and eliminating unnecessary promise allocations under backpressure, resulting in significant benchmark speedups. The build process was improved by enabling the -fvisibility compiler flag, increasing startup speed by about 33% without breaking addon compatibility.
  • pull/65625, [pull/65526](https://github.com/pull/65526]

• Bug fixes and stability improvements: A use-after-free bug in CleanupHookThunkRun was fixed by caching fields before running cleanup hooks, with regression tests added. A live lock issue in LockManager::ProcessQueue() was resolved by waking environments only when requests can proceed, preventing continuous wake cycles without progress.
  • pull/65630, [pull/65520](https://github.com/pull/65520]

• Collaboration and documentation: Documentation was added to clarify procedures for collaborators using the commit queue, fast-track, stale automation, and saved triage views, as well as clarifying the semantics of needs-ci and reviewer expectations. This improves project workflow and contributor understanding.
  • pull/65671

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

Key Closed Pull Requests

1. vfs: integrate with CJS and ESM module loaders: This pull request integrates the Virtual File System (VFS) with both CommonJS (CJS) and ECMAScript Module (ESM) loaders in Node.js, enabling require() and import to resolve files served by the node:vfs API by mounting VFS instances into a reserved namespace under a device-null path, implementing efficient path dispatch and cache purging mechanisms, and ensuring module identity and loader cache correctness without interfering with the real filesystem.

• URL: pull/63653

• Associated Commits: 66713, 90d8e, b28a0, d1199, f94cd, ee06f, 7bedf, 133a8, cefef, 722e1, e7dd6, de17e, a17ee, 02351, e3784, 7e94c, 2203b, f2f7b, 2462d, 90225, 27169, 6fafe, 6e3f1, a9571, ffd68, 7b6e3, 2e463, 5b71a, 30d51, 337c1, 0d5fb

2. Fix/issue 314: This pull request addresses issue 314 by reducing the internal field count of the FileHandle class from seven to six to comply with V8's JSObject::kMaxEmbedderFields limit, thereby enabling debug builds to start successfully while maintaining support for the closing promise functionality.

• URL: pull/65643

• Associated Commits: b6fbc, ee3c1, 30931, 6bb32, f933b, 3cec8, 5594a, 7e396, dbf62, e0916, d211b, 32832, 2107b, 9ef74, 75151, 3a562, 23728, 39c44, cbb7b, 383f0, 907ab, 61198, 52709, b4ae0, c63e2, 263d8, 3e36f, 9475a, e02ee, 30985, 2aabc

3. http2: emit ERR_HTTP2_INVALID_SESSION async instead of throwing synchronously: This pull request modifies the HTTP/2 implementation to emit the ERR_HTTP2_INVALID_SESSION error asynchronously rather than throwing it synchronously, ensuring that the session's 'close' event is emitted before any stream 'close' events during session shutdown, particularly when the underlying socket is abruptly destroyed, and includes new tests to validate the correct event ordering and asynchronous error handling.

• URL: pull/63422

• Associated Commits: bac13, e922a, 857a0, a538e, df4cc, d0b96, e1607, 94593, 9dbe1, 7f650, 71ca4, 72de8

Other Closed Pull Requests

• TypeScript support in REPL: This pull request introduces experimental TypeScript support to the Node.js REPL, which can be enabled optionally using the --experimental-repl-typescript flag. This addition aims to enhance the REPL experience by allowing TypeScript code execution directly within the environment.
  pull/64077

• SQLite NULL to undefined conversion: Two pull requests add a setReadNullAsUndefined(boolean) method and a statement-level flag to the StatementSync class in the Node.js SQLite binding. These changes enable converting SQL NULL values to JavaScript undefined in various row-reading methods, improving handling of null/undefined distinctions without affecting function arguments or write operations.
  pull/59462, pull/61472

• HTTP module improvements and debugging: One pull request proposes coalescing chunked writes during auto-corking to optimize HTTP performance, while another adds optional debug logging to the socketOnTimeout function to improve diagnosis of HTTP timeout issues. These changes aim to enhance HTTP module performance and debugging capabilities without impacting production performance.
  pull/64987, pull/59514

• Error message and path handling fixes: A pull request fixes error message handling in fs.rmSync by removing duplicated and corrupted path information and normalizing Windows paths for consistent cross-platform error outputs. Another pull request fixes an infinite loop in fs.realpathSync when resolving nested symbolic links by correctly resolving link targets and adding tests.
  pull/61233, pull/61391

• Test improvements and benchmark additions: This pull request adds a new environment variable to run all benchmark configurations, introduces benchmark tests for multiple modules, updates documentation on benchmarks, and renames test files for consistency. These changes improve test coverage and documentation clarity for benchmarking in Node.js.
  pull/59919

• Test snapshot normalization enhancements: A pull request improves test snapshot normalization by making cwd path stripping URL-safe and boundary-aware, correctly handling file:// URLs and avoiding corruption of non-path tokens. It also updates tests to use a shared transform pipeline and adds regression coverage for URL tokens and percent encoding.
  pull/61356

• ESM module error import trace: This pull request adds an import trace section to error outputs for errors thrown during ESM module evaluation, revealing the chain of module imports leading to the failure. This enhancement improves debugging without altering existing stack formatting or global error behavior.
  pull/61612

• HTTP headers documentation update: The documentation for http.request() is updated to clarify that the headers option can be provided as a flat array of alternating header names and values, aligning with formats used in response.writeHead() and request.rawHeaders. The update also fixes markdown linting and link formatting issues.
  pull/58810

• File watching CLI option: A new non-breaking CLI option --watch-pattern is added to Node.js to enable watching files and directories using glob patterns. This addresses issues with the existing --watch-path option where certain glob characters in filenames could cause unintended breakage.
  pull/59345

• Readline question history skip option: This pull request introduces a boolean skipHistory option to readline.Interface.question() that prevents user input from being saved in the readline history when set to true. This feature enhances privacy for sensitive inputs like passwords while maintaining default behavior when false, with comprehensive tests included.
  pull/59450

• REPL multiline subprompt customization: The REPL subprompt for multiline input is made customizable, replacing the previously fixed "|" prompt with a user-defined string. This change enhances the flexibility and user experience of multiline statements in the Node.js REPL.
  pull/59566

• Nomination process automation script: A pull request adds a script to automate and simplify the currently manual nomination process, reducing the effort required despite limitations in creating polls via the API. This aims to streamline community nomination workflows.
  pull/60824

• Diagnostics channel iterator tracing: This pull request adds a new traceIterator function to the diagnostics_channel module, enabling tracing of functions that return iterators by instrumenting both the function and each iteration. This addresses the need to track completion and results of iterator-based operations.
  pull/61686

• WinGet release manifest automation: A GitHub action is introduced that automatically updates and submits the latest stable Node.js release manifest to WinGet using the microsoft/winget-create tool whenever a new release is published. This automates the release manifest maintenance process.
  pull/56774

• perf_hooks documentation correction: The perf_hooks documentation is corrected by updating eventLoopUtilization() examples to properly use the performance object instead of importing eventLoopUtilization directly. A clarifying note is added that this method must be accessed via performance.
  pull/60421

• readdir recursive Buffer argument fix: This pull request fixes a bug where calling readdir with a Buffer argument in recursive mode incorrectly produced an ERR_INVALID_ARG_TYPE error. The fix ensures readdir correctly returns an array of Buffers or Dirents depending on the options provided.
  pull/60936

• process.loadedModules property: A new process.loadedModules property is added to return an array of public core module names loaded during the current process execution. This provides a cleaner and documented alternative to the existing undocumented process.moduleLoadList.
  pull/61330

• Static analysis and null pointer checks: This pull request fixes static analysis warnings in the SQLite and Web Storage modules by adding necessary null pointer checks and error handling. These changes prevent potential crashes and improve code safety without altering existing functionality.
  pull/61380

• ProcessWrap stdio options validation: The robustness of ProcessWrap::ParseStdioOptions() is enhanced by validating that each entry in options.stdio is an object to prevent fatal errors caused by prototype pollution. A regression test is included to ensure Node.js does not abort when encountering polluted Array.prototype entries.
  pull/61978

• Stream pipeline validation: This pull request adds validation for streams used in the pipeline function within the Node.js stream module, including tests covering various stream argument scenarios. This aims to improve robustness and correctness of stream handling.
  pull/62214

• Stream consumers documentation reference: A brief reference to the node:stream/consumers utility functions is added to the main stream documentation to improve discoverability. This helps developers avoid writing manual boilerplate when consuming streams.
  pull/62613

• Experimental node:validator module: An experimental built-in node:validator module is introduced, providing synchronous, JSON-Schema-inspired input validation for simple REST-style payloads. It features a reusable Schema class with support for common data types and constraints, non-throwing validation results, default value application, schema composition, and compile-time schema validation, gated behind an opt-out experimental flag.
  pull/62927

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.

Access Last Week's Newsletter:

• Link