Weekly GitHub Report for Node - 2024-07-17 21:23:24

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.

---

I. Issues

1.1 Open Issues

Open Issues This Week: 18

Summarized Issues:

• Erroneous Error Messages in Node.js: This issue describes a bug in Node.js where an erroneous error message is displayed, indicating that a package.json file is missing when attempting to import a module, even though the actual missing file is index.js. This misleading error message can cause confusion for developers trying to debug their applications. The issue highlights the need for more accurate error reporting in the Node.js runtime.
  • github.com/nodejs/node/issues/53806

• Module Import and Path Resolution Issues: This issue describes a bug in the test_runner subsystem where using module mocking with the --experimental-test-module-mocks flag causes all future ECMAScript Module (ESM) imports to incorrectly use CommonJS (CJS) path resolution, leading to unexpected behavior in module imports. This can result in modules not being found or incorrect modules being loaded, disrupting the testing process. The issue underscores the importance of consistent module resolution mechanisms.
  • github.com/nodejs/node/issues/53807

• Segmentation Faults in C++ Addon: This issue reports that version 22.4.1 of a C++ addon for Node.js causes segmentation faults on a Linux Debian platform, whereas previous versions 20.15.1 and 20.14.0 do not exhibit this problem. This regression can lead to crashes and instability in applications relying on the addon. The issue calls for an investigation into the changes introduced in the newer version.
  • github.com/nodejs/node/issues/53810

• Confusing Error Messages in ReadableStream: This issue describes a confusing error message returned by ReadableStream.from({}) in Node.js v22.4.1, where the error should ideally indicate that the value is not iterable but instead throws a TypeError related to FunctionPrototypeCall. This can mislead developers about the actual cause of the error. The issue highlights the need for more intuitive and accurate error messages.
  • github.com/nodejs/node/issues/53819

• Enhancements to Node.js Command Line Interface: This issue proposes adding an optional --root-directory flag to the node --run command to limit the recursive search for package.json and the addition of /node_modules/.bin paths to a specified directory, which is particularly useful in monorepo setups to avoid discrepancies between local and CI environments. Another proposal suggests adding support for running bin scripts in package.json using a new node --run-bin or similar command, enhancing the node task runner to handle bin scripts in addition to scripts during local development.
  • github.com/nodejs/node/issues/53831
  • github.com/nodejs/node/issues/53845

• Test Failures and Platform-Specific Issues: This issue describes a test failure in the Node.js project where the parallel/test-worker-node-options test fails on IBM i with an assertion error, indicating that the expected value 'foo' does not match the actual empty string, and suggests that IBM i might need a similar conditional fix as SmartOS. Another issue highlights a problem where the stack trace does not include the line responsible when a ReadableStream read operation fails, making it difficult to identify the source of the error.
  • github.com/nodejs/node/issues/53852
  • github.com/nodejs/node/issues/53858

• Refactoring and Memory Management in Test Runner: This issue addresses the need to refactor the test_runner in the Node.js project so that it does not directly access process.argv and process.cwd() within the run() function, but instead captures this information earlier and passes it as options to run(). Another issue involves removing global event handlers registered by the test runner on the process after all tests are completed to prevent memory leaks and warnings about exceeding the maximum number of listeners.
  • github.com/nodejs/node/issues/53867
  • github.com/nodejs/node/issues/53868

• Clarifying Web Storage Behavior: This issue is about clarifying the behavior of Web Storage in Node.js, specifically how session storage and local storage are scoped to the current process, the use of --localstorage-file for local storage origin, and other details such as simultaneous access by multiple processes and the 10MB quota. This clarification is necessary to prevent misunderstandings and ensure proper usage of Web Storage in Node.js applications.
  • github.com/nodejs/node/issues/53871

• API Enhancements and Feature Requests: This issue proposes the addition of an API to detect if code is being executed via the --import flag in Node.js, as current methods like isMainThread and parsing the stack trace are insufficient. Another issue is about adding support for the sqlite.loadExtension feature in the Node.js project to enable loading SQLite extensions, similar to the APIs provided by other libraries like better-sqlite3, node-sqlite3, @db/sqlite, and bun:sqlite.
  • github.com/nodejs/node/issues/53882
  • github.com/nodejs/node/issues/53898

• Automated Comment Requests by @nodejs-github-bot: This issue questions the necessity of the @nodejs-github-bot's automated comment requests for team reviews, suggesting that manual notifications might be more appropriate given the bot's limitations and the current monitoring practices. The issue raises concerns about the efficiency and relevance of automated notifications in the review process.
  • github.com/nodejs/node/issues/53897

• Crashes and Hangs on macOS with M1 Chip: This issue describes a problem where Node.js version 22.5.0 crashes or hangs during various operations on macOS 15.0 with an M1 chip, particularly when running scripts that involve file system operations, leading to fatal errors related to the V8 engine's object creation context. This issue highlights the need for compatibility and stability improvements for Node.js on newer macOS versions and hardware.
  • github.com/nodejs/node/issues/53902

• Inconsistent fs.watch Events on Windows: This issue describes a bug in Node.js on Windows where recursive fs.watch on a directory junction produces inconsistent "change" events when files are deleted, depending on whether the parent directory is actively being observed by any process. This inconsistency can lead to unreliable file system monitoring and unexpected behavior in applications.
  • github.com/nodejs/node/issues/53903

• Documentation Updates for Experimental Features: This issue highlights the need to update the Node.js API documentation to indicate that the --experimental-sqlite flag is required to use the node:sqlite module introduced in Node.js v22.5.0, to prevent confusion and unnecessary bug reports. Proper documentation is essential for developers to correctly utilize new and experimental features.
  • github.com/nodejs/node/issues/53906

• Bugs in fs.openAsBlob() Function: This issue describes a bug in the fs.openAsBlob() function where the slice() method does not return the expected portion of the blob, specifically when called with no arguments or chained slices, resulting in incorrect blob lengths upon reading. This bug can lead to data integrity issues and incorrect file handling in applications.
  • github.com/nodejs/node/issues/53908

1.2 Top 5 Active Issues:

We consider active issues to be issues that have generated much discussion in the issue's comments.

1. enable corepack by default: This issue is about enabling Corepack by default in Node.js to ensure developers use the same version of pnpm specified in the packageManager field of package.json. The current problem is that developers often forget to enable Corepack, leading to inconsistencies in the package manager version used across different projects.

   • The comments discuss various aspects, including the feasibility of enabling Corepack by default, the potential security implications, the relationship between Node.js and npm, and the broader impact on the developer experience. There are differing opinions on whether Corepack should be enabled by default, with some advocating for its benefits in managing package manager versions and others raising concerns about its compatibility with npm and the added complexity. The discussion also touches on the need for clear documentation and governance regarding the inclusion of package managers in Node.js.
   • Number of comments: 122

2. Discussion: New “ESM by default” mode: This issue discusses the proposal of introducing a new mode in Node.js where the default module system is ECMAScript Modules (ESM) instead of CommonJS (CJS). The proposal suggests enabling this mode via a flag, with the potential for it to become the default in a future major release, and outlines various use cases and changes required to support this mode.

   • The comments section includes a detailed discussion on the feasibility and implications of changing the default module system, concerns about ecosystem breakage, and various technical considerations such as handling shebangs, URL parsing for entry points, and the impact on existing tools and workflows. There is a consensus on the need for a flag to enable this mode initially, with further discussions on how to handle specific edge cases and potential breaking changes.
   • Number of comments: 98

3. .env file support issue tracker: This issue is a follow-up to a previous pull request to track the development process and address questions regarding the implementation of .env file support in Node.js. The issue includes a list of tasks and questions to be resolved, such as defining the syntax of .env files, supporting multiple --env-file parameters, and deciding on the behavior when an .env file does not exist.

   • The comments discuss various aspects of .env file support, including whether to throw errors for non-existing files, the precedence of environment variables over .env file values, and the potential addition of a programmatic API. There are also debates on the format of .env files, with suggestions for using JSON, YAML, or TOML, and the need for multi-line value support. Some comments highlight issues with the current implementation, such as incorrect handling of comments and the need for environment variable interpolation. The discussion also touches on the possibility of supporting encrypted .env files and the importance of defining a precise specification for the .env file format.
   • Number of comments: 55

4. Proposal for a simple, universal module loader hooks API to replace require() monkey-patching: This issue proposes a new synchronous, in-thread, universal module loader hooks API to replace the current require() monkey-patching in Node.js. The goal is to simplify the customization of module loading for both CommonJS (CJS) and ECMAScript Modules (ESM), making it easier for the ecosystem to migrate to ESM while maintaining backward compatibility.

   • The comments discuss various aspects of the proposal, including its potential benefits for third-party tools, the challenges of the current off-thread hooks, and the need for a universal API that works for both CJS and ESM. There is also a debate on whether to keep the off-thread hooks, with some suggesting that synchronous hooks could simplify the module loading process and reduce maintenance burdens. The discussion includes technical details on how the new hooks could be implemented and their impact on existing tools and workflows.
   • Number of comments: 47

5. Discussion: Name of the flag for the “ESM by default” mode: This issue is about deciding the name for a new flag in Node.js that will enable "ESM by default" mode, which is currently under discussion. The flag needs to start with --experimental and should either take a value or have an obvious opposite to allow users to opt back into the previous CommonJS-first behavior.

   • The comments discuss various naming options for the flag, including --experimental-type, --experimental-default-type, and --experimental-implicit-type, with concerns about user confusion and breaking changes. There is also a debate on whether to expand the scope of the existing --input-type flag or create a new one. The conversation includes suggestions for short flag versions and the potential deprecation of existing short flags to accommodate new ones. The discussion concludes with a call for consensus and a vote on the preferred naming option.
   • Number of comments: 42

1.3 Top 5 Quiet Issues:

We consider quiet issues to be issues that have been opened in this project for the longest time. The team should work together to get these issues resolved and closed as soon as possible.

1. process.report.getReport slower from 20.2.0 to 20.3.0 on Linux: This issue highlights a significant performance regression in the process.report.getReport function between Node.js versions 20.2.0 and 20.3.0 on Linux systems. The slowdown is attributed to a change in the libuv library, which now reads CPU frequency information for each CPU individually, rather than assuming the same information for all CPUs.

   • Open for 364 days, 23 hours, 33 minutes

2. Changelog is not rendered on github: This issue highlights a problem where the changelog for Node.js version 18 is not being rendered on GitHub due to a timeout error. The user suggests that the project should consider hosting the changelogs directly on the nodejs.org website to avoid such issues.

   • Open for 364 days, 17 hours, 53 minutes

3. v8-updates/test-linux-perf.js is flaky: This issue is about the flakiness of the v8-updates/test-linux-perf.js test in the Node.js project, which has been open for 363 days. The problem seems to be related to the robustness of checking the output of perf script, and the suggestion is to simplify the test by only verifying that the perf map is produced, as the current method may be too dependent on the machine's state.

   • Open for 363 days, 01 hours, 19 minutes

4. test/internet/test-net-autoselectfamily-timeout-close times out on daily internet tests CI: This issue pertains to the internet/test-net-autoselectfamily-timeout-close test, which is timing out during the daily internet tests on the CI. The problem has persisted for 362 days and involves the test suite that reaches out to other servers across the internet, causing the test to fail with a timeout error.

   • Open for 362 days, 12 hours, 31 minutes

5. crypto.createPrivateKey no longer throws TypeError for missing passphrase: This issue pertains to the crypto.createPrivateKey function in Node.js, which no longer throws a TypeError for a missing passphrase when attempting to create a private key from an encrypted key. Instead of the expected ERR_MISSING_PASSPHRASE error, the function now throws an ERR_OSSL_CRYPTO_INTERRUPTED_OR_CANCELLED error, indicating a change in behavior possibly due to an OpenSSL upgrade.

   • Open for 362 days, 01 hours, 29 minutes

1.4 Closed Issues

Closed Issues This Week: 20

Average Issue Close Time (This Week): 63.87 days

Summarized Issues:

• CLI Commands for Node.js Version Management: This issue proposes adding CLI commands "node use vx" and "node install vx" to allow changing and installing Node.js versions directly within Node.js, similar to the functionality provided by nvm. This would streamline the process of managing Node.js versions without needing external tools. The feature aims to enhance user convenience and efficiency.
  • github.com/nodejs/node/issues/50958

• Regression and TypeError Issues: This issue describes a regression in Node.js version 21.4.0 where using the esm package results in a TypeError and the content of esm.js being dumped to the console, which did not occur in version 21.3.0. The regression impacts the stability and usability of the esm package. Users are experiencing unexpected behavior and errors.
  • github.com/nodejs/node/issues/51081

• Debugging and Unhandled Rejection Issues: This issue describes a problem where the correct implementation of an internal function in the stream/web module causes debuggers to incorrectly detect an unhandled rejection, leading to debugging difficulties in environments like VSCode and Chrome. The issue complicates the debugging process and affects developer productivity. A feature request to enhance the uncaughtExceptionMonitor event is also discussed to provide more insight into unhandled promises.
  • github.com/nodejs/node/issues/51093
  • github.com/nodejs/node/issues/51201

• Test Coverage Options: This issue proposes adding coverage-path and coverage-ignore-path options to the test runner to allow users to specify which files and directories should be included or excluded from test coverage reports. This feature would provide more control over test coverage metrics. Another issue discusses excluding test files from the coverage report to avoid skewed metrics.
  • github.com/nodejs/node/issues/51222
  • github.com/nodejs/node/issues/53508

• Buffer and WASM Crash: This issue describes a bug in Node.js v22.2.0 where using the deprecated new Buffer() API in conjunction with WebAssembly (WASM) causes a crash due to an undefined filename in the stack trace, which does not occur in earlier Node.js versions. The crash affects the stability of applications using these features. Users are advised to avoid deprecated APIs.
  • github.com/nodejs/node/issues/53075

• Boolean Flag Parsing Issue: This issue addresses a problem with the parseArgs function in Node.js where a boolean flag with a default value of true cannot be set to false using a --no prefix. The issue discusses potential solutions and a fix implemented in a related pull request. This affects the flexibility and correctness of command-line argument parsing.
  • github.com/nodejs/node/issues/53095

• .env File Parsing Bug: This issue describes a bug where having a space between the equals sign and a quoted value in an .env file causes the value to be parsed incorrectly as an unquoted string. This results in the inclusion of the quotes in the variable's value, leading to unexpected behavior in applications relying on environment variables.
  • github.com/nodejs/node/issues/53461

• Documentation Highlighting Bug: This issue describes a bug in the Node.js documentation where attempting to highlight text causes the page to scroll up excessively. This makes it difficult to select and copy specific portions of text, affecting the usability of the documentation.
  • github.com/nodejs/node/issues/53594

• FinalizationRegistry Callback Issue: This issue describes a problem where the FinalizationRegistry in Node.js version 22.4.1 on a Darwin platform is not correctly invoking its callback when a setTimeout object is garbage collected. Unlike WeakRef, which works as expected, this issue affects the reliability of garbage collection callbacks.
  • github.com/nodejs/node/issues/53805

• Fetch Function TypeError: This issue describes a problem where using the fetch function in Node.js version 22.0.0 on a Darwin platform results in a TypeError. The error indicates that a class extends a value that is not a constructor or is null, potentially due to a new WebSocket native implementation in Node.
  • github.com/nodejs/node/issues/53809

• Security Policy and URI Handling: This issue questions why data: URIs are treated differently from file: URIs in the Node.js security policy. It highlights a potential security vulnerability where attackers can bypass network import restrictions by embedding non-network imports in data: URLs.
  • github.com/nodejs/node/issues/53815

• fsPromises.glob Exclude Callback Bug: This issue describes a bug in the fsPromises.glob function where it fails to call the exclude callback with a Dirent object when the withFileTypes option is set to true. Instead, it only prints the directory name, affecting the functionality of the exclude callback.
  • github.com/nodejs/node/issues/53821

• Windows Node Installation Command: This issue is about implementing the command fnm env --use-on-cd | Out-String | Invoke-Expression for Windows node installation. The discussion is in the context of the Node.js installation page, aiming to improve the installation process on Windows.
  • github.com/nodejs/node/issues/53824

• Multidimensional Arrays in JavaScript: This issue discusses the difficulty of instantiating multidimensional arrays in JavaScript and proposes a new method to simplify the process. It also seeks guidance on contributing to the JavaScript standard, aiming to enhance array handling in the language.
  • github.com/nodejs/node/issues/53843

• Rare Crash with MySQL and Sequelize: This issue describes a rare crash in Node.js 18 running on a Docker image (node:18-alpine) when executing a MySQL command using the Sequelize API. The crash results in a fatal error related to internal state values, affecting the stability of applications using these technologies.
  • github.com/nodejs/node/issues/53854

• Miscellaneous Issues: This issue pertains to a problem or discussion linked to a specific URL (https://stackblitz.com/connect/70dbe416) within the Node.js GitHub project, as indicated by the provided title and URL, but lacks additional descriptive details or comments in its body. Another issue pertains to the website domdiservices.store, which involves communication, marketing, and the distribution and sale of products and services aimed at assisting individuals.
  • github.com/nodejs/node/issues/53874
  • github.com/nodejs/node/issues/53887

• ERR_UNKNOWN_BUILTIN_MODULE Error: This issue describes a problem where attempting to require the node:sqlite module in Node.js version 22.5.0 results in an ERR_UNKNOWN_BUILTIN_MODULE error. Despite the module being mentioned in the release notes, it is suggested that the module requires the --experimental-sqlite flag to be used.
  • github.com/nodejs/node/issues/53905

1.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open issues within the past week 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 issues from the past week.

---

II. Pull Requests

2.1 Open Pull Requests

Open Pull Requests This Week: 45

Pull Requests:

• Documentation Enhancements: Several pull requests aim to improve the Node.js documentation by adding missing information, clarifying existing content, and updating guides. These changes include expanding the troubleshooting section, updating the release guide, and adding details about localStorage and sessionStorage. Additionally, a missing word was added to the "Startup snapshot support" section, and a note about the --experimental-sqlite feature was included.
  • github.com/nodejs/node/pull/53808
  • github.com/nodejs/node/pull/53828
  • github.com/nodejs/node/pull/53881
  • github.com/nodejs/node/pull/53864
  • github.com/nodejs/node/pull/53907

• Code Refactoring and Optimization: Multiple pull requests focus on refactoring and optimizing the Node.js codebase to improve performance and maintainability. These include replacing strcmp with std::string_view, refactoring the get_format function, and relocating the toNamespacedPath function call. Additionally, the AESCipherTraits::AdditionalConfig was streamlined, and redundant option parsing in the file system module was eliminated.
  • github.com/nodejs/node/pull/53813
  • github.com/nodejs/node/pull/53872
  • github.com/nodejs/node/pull/53875
  • github.com/nodejs/node/pull/53890
  • github.com/nodejs/node/pull/53861

• Bug Fixes and Error Handling: Several pull requests address various bugs and improve error handling in the Node.js project. These fixes include throwing a TypeError in the getIterator function, enhancing error messages for missing indexes, and fixing a regression in the run({ watch: true }) functionality. Additionally, the close function bug and the 'No creation context' error were resolved.
  • github.com/nodejs/node/pull/53825
  • github.com/nodejs/node/pull/53859
  • github.com/nodejs/node/pull/53866
  • github.com/nodejs/node/pull/53910

• Feature Reversions and Removals: Some pull requests focus on reverting or removing features due to unresolved issues or security concerns. The --experimental-network-imports feature was removed, and a previous commit adding a V8 fast API to the closeSync function was reverted due to regressions.
  • github.com/nodejs/node/pull/53822
  • github.com/nodejs/node/pull/53904

• Module and Dependency Updates: Various pull requests update modules and dependencies to improve compatibility and performance. These updates include minifying the 'undici' dependency, updating the gcovr tool to version 7.2, and updating the Python linter, Ruff, to version 0.5.2.
  • github.com/nodejs/node/pull/53870
  • github.com/nodejs/node/pull/53896
  • github.com/nodejs/node/pull/53909

• Security and Stability Improvements: Several pull requests aim to enhance the security and stability of the Node.js project. These include updating the SecureContext member functions, ensuring the v8_pointer_compression_sandbox feature is enabled, and replacing the ToLocalChecked() method with ToLocal() in the node-file module.
  • github.com/nodejs/node/pull/53883
  • github.com/nodejs/node/pull/53884
  • github.com/nodejs/node/pull/53869

• Test and CI Enhancements: Multiple pull requests focus on improving the testing and continuous integration (CI) processes. These include adding support for sqlite to the JavaScript subsystems, cleaning up global event listeners after tests, and adding a workflow to synchronize lists in the README file with GitHub teams.
  • github.com/nodejs/node/pull/53911
  • github.com/nodejs/node/pull/53878
  • github.com/nodejs/node/pull/53901

• Miscellaneous Improvements: Various pull requests address miscellaneous improvements in the Node.js project. These include adding a new collaborator, updating the SLACK_TITLE in the invalid commit workflow, and re-enabling Codecov comments.
  • github.com/nodejs/node/pull/53895
  • github.com/nodejs/node/pull/53912
  • github.com/nodejs/node/pull/53891

2.2 Closed Pull Requests

Closed Pull Requests This Week: 57

2.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open pull requests within the past week 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 pull requests from the past week.

---

III. Commits

3.1 Commits

Commits This Week: 46

Summarized Commits:

• File System Module Enhancements: Several commits focus on improving the file system module, including removing unnecessary validation of option arguments, ensuring the dirent object is correctly passed to the withFileTypes option, and moving ToNamespacedPath directory calls to C++. These changes enhance the module's efficiency and correctness.

• Metadata and Documentation Updates: Updates to project metadata and documentation include moving 'anonrig' to the TSC voting members, correcting the casing of GitHub handles, moving MylesBorins to emeritus status, and updating the email address of 'anonrig'. These changes ensure accurate representation and acknowledgment of contributors.

• Release Management: The release date for version 22.5.0 was updated in the CHANGELOG_V22.md file, and the script for posting release information on nodejs.org was updated. These commits help maintain accurate release schedules and streamline the release process.

• Version 22.5.0 Features: Version 22.5.0 introduces several new features, including websockets in the HTTP module, a node:sqlite module, __esModule in require()'d ESM, a matchesGlob method in the path module, and postMessageToThread in the worker module. These additions expand the functionality and capabilities of the Node.js platform.

• Test Runner Improvements: The test runner received multiple updates, such as refactoring snapshot tests, introducing a filePath getter to TestContext and SuiteContext classes, consolidating option parsing, and fixing the escaping mechanism in snapshot tests. These changes improve the robustness and maintainability of the test runner.

• Performance Optimizations: Performance enhancements include exposing the getCategoryEnabledBuffer function to avoid repeated C++ calls for trace category checks and reducing unnecessary string copies. These optimizations improve the efficiency of the Node.js runtime.

• Security and Stability Fixes: Several commits address security and stability issues, such as preventing segmentation faults in SQLite, handling bypassing network imports via data URLs, and addressing a crash issue when emitting a deprecation warning for new Buffer(). These fixes enhance the reliability and security of the platform.

• Tooling and Configuration Updates: Updates to project tools and configurations include utilizing v8_features.json for populating config.gypi, updating the PR label configuration to include node_sqlite.c, and adding the term "PTAL" to the project's glossary. These changes improve the project's tooling and contributor experience.

• Inspector and Debugging Enhancements: Enhancements to the inspector for streams and the introduction of a new benchmark for 'require-esm' functionality improve debugging and performance analysis capabilities. These updates help developers diagnose and optimize their applications more effectively.

• Platform and Compatibility Updates: Refactoring platform utility methods, cleaning up references to OSX, and updating references to specific sections of the ECMA-262 standard ensure better platform compatibility and code clarity. These changes maintain the project's alignment with evolving standards and platforms.

• Test and Workflow Adjustments: Disabling the test-asan workflow due to deprecation issues and removing the undocumented plan option from the test_runner's run() function streamline the project's testing and CI workflows. These adjustments help maintain a smooth and efficient development process.

• TLS and Networking Enhancements: The introduction of the setKeyCert() method to the tls.Socket class and improvements in handling network imports via data URLs enhance the project's networking capabilities. These updates provide more flexibility and security in network-related operations.

• Error Handling and Logging: Reducing redundant logging from dependency updaters and minimizing unnecessary errors during file system operations involving glob patterns improve the project's error handling and logging mechanisms. These changes help maintain cleaner logs and reduce noise.

• Acknowledgments and Contributor Recognition: Updates to documentation to include Rafael in the acknowledgments for the latest security release and the use of mock.callCount() in examples ensure proper recognition of contributors and provide clearer examples for users. These updates foster a more inclusive and informative documentation.

• Miscellaneous Fixes and Enhancements: Various other commits address minor issues such as typos in the URL module, updating the 'nbytes' dependency, and relocating the loadEnvFile function. These small but important changes contribute to the overall quality and maintainability of the project.

---

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, or created at least 1 pull request in the past month.

Contributor	Commits	Pull Requests	Issues
RedYetiDev	1	32	5
anonrig	0	35	2
Node.js GitHub Bot	25	0	0
Yagiz Nizipli	24	0	0
RafaelGSS	8	8	0
joyeecheung	0	8	5
Aviv Keller	12	0	0
tniessen	0	12	0
jakecastelli	4	7	0
targos	0	10	1
Tobias Nießen	10	0	0
Joyee Cheung	10	0	0
aduh95	0	10	0
legendecas	0	9	0
Antoine du Hamel	8	0	0
Michael Dawson	8	0	0
Richard Lau	8	0	0
mhdawson	0	7	1
zcbenz	0	8	0
cjihrig	2	4	1
Michaël Zasso	7	0	0
Chengzhong Wu	7	0	0
Cheng	6	0	0
Rafael Gonzaga	5	0	0
richardlau	0	5	0
benjamingr	0	4	1
rotu	0	1	4
Filip Skokan	4	0	0
codediverdev	2	2	0
jasnell	0	4	0
GeoffreyBooth	0	3	1
Colin Ihrig	3	0	0
Vinicius Lourenço	3	0	0
Benjamin Gruenbaum	3	0	0
ehsankhfr	1	2	0
panva	0	3	0
danielbayley	0	3	0
H4ad	0	3	0
mfdebian	0	3	0
lirantal	0	3	0
mcollina	0	1	2
codebytere	0	3	0
himself65	0	2	1
ronag	0	0	3
Daniel Bayley	2	0	0
mscdex	1	1	0
Daeyeon Jeong	2	0	0
James M Snell	2	0	0
Geoffrey Booth	2	0	0
theanarkh	1	1	0
Zhenwei Jin	2	0	0
marco-ippolito	0	2	0
YaIWon	0	2	0
robhogan	0	1	1
vmoroz	0	2	0
LeoDog896	0	1	1
Emiltayeb	0	2	0
cloydlau	0	2	0
abmusse	0	1	1
daeyeon	0	2	0
Kay-Yuan	0	2	0
corp-jones-damarcus	0	2	0
Rekl0w	0	2	0
Deuces9ers	0	0	2
ajvincent	0	0	2
bojavou	0	0	2
manoraj	0	0	2
trentm	0	0	2
Jonas	1	0	0
Mohit Malhotra	1	0	0
Jordan Harband	1	0	0
Julian Kniephoff	1	0	0
Myles Borins	1	0	0
Mert Can Altin	1	0	0
KAYYY	1	0	0
Sébastien Règne	1	0	0
Aras Abbasi	1	0	0
Afanasii Kurakin	1	0	0
Cloyd Lau	1	0	0
Igor Sheludko	1	0	0
Paolo Insogna	1	0	0
Natalia Venditto	1	0	0
Claudio W	1	0	0
Abdirahim Musse	1	0	0
Alfredo González	1	0	0
Mathis Wiehl	1	0	0
Elliot Goodrich	1	0	0
Emil Tayeb	1	0	0
Leonardo Peixoto	1	0	0
Cristian Barlutiu	1	0	0
René	1	0	0
Eliphaz Bouye	1	0	0
Rob Hogan	1	0	0
Marco Ippolito	1	0	0
Jay Kim	1	0	0
synapse	0	1	0
eliphazb	0	1	0
shivam999876	0	1	0
ShenHongFei	0	1	0
Renegade334	0	1	0
lemire	0	1	0
mildsunrise	0	1	0
DanielVenable	0	1	0
sky-39	0	1	0
cola119	0	1	0
bmeck	0	1	0
peixotoleonardo	0	1	0
elliotgoodrich	0	1	0
AlirezaEbrahimkhani	0	1	0
afanasy	0	1	0
bpasero	0	1	0
ShogunPanda	0	1	0
anfibiacreativa	0	1	0
ovflowd	0	1	0
regseb	0	1	0
MylesBorins	0	1	0
ljharb	0	1	0
JLHwung	0	1	0
YieldRay	0	1	0
MOHIT51196	0	1	0
WontonSam	0	1	0
Trott	0	1	0
mertcanaltin	0	1	0
gabrielschulhof	0	1	0
JulianKniephoff	0	1	0
syi0808	0	1	0
ibrahimskh	0	1	0
guybedford	0	1	0
shyam66666	0	1	0
JonasBa	0	1	0
huseyinacacak-janea	0	1	0
tsabolov	0	1	0
Kikobeats	0	1	0
taniishkaaa	0	1	0
EddieAbbondanzio	0	1	0
MattiasBuelens	0	1	0
tie	0	1	0
029A-h	0	0	1
ido-pluto	0	0	1
sparecycles	0	0	1
bcherny	0	0	1
rozzilla	0	0	1
Ashvith10	0	0	1
joepie91	0	0	1
BourgoisMickael	0	0	1
demonztt1	0	0	1
ghost	0	0	1
anonhostpi	0	0	1
sachinmali287	0	0	1
saurabhdaware	0	0	1
guoh27	0	0	1
danielng620	0	0	1
mishaled	0	0	1
lachrist	0	0	1
nicholaswmin	0	0	1
ai	0	0	1
webdrakib	0	0	1
KostiantynO	0	0	1
orinatic	0	0	1
skypesky	0	0	1
bibitoo	0	0	1
Mrgaton	0	0	1
x-yuri	0	0	1
xav-ie	0	0	1
AriPerkkio	0	0	1
ericmorand	0	0	1
redactedprism	0	0	1
Fusl	0	0	1
Jason3S	0	0	1
Triskae	0	0	1
PuruVJ	0	0	1
jdiaz-dev	0	0	1
AcePeed	0	0	1
isaacs	0	0	1
realriccio	0	0	1
analogic	0	0	1
priyanshtrivedi	0	0	1
EmilianoBecerra	0	0	1
kristoffer-zliide	0	0	1
mbrevda	0	0	1
muturgan	0	0	1
Tina1L	0	0	1
OliverJAsh	0	0	1
lucacasonato	0	0	1
xicilion	0	0	1
meyfa	0	0	1
lights0123	0	0	1
rentalhost	0	0	1
Heyitsquoracom	0	0	1
Tekshan98Madhawa	0	0	1
cjinhuo	0	0	1
dakhnod	0	0	1
ChALkeR	0	0	1
DominusKelvin	0	0	1
tvmoo9	0	0	1
eligrey	0	0	1
CukitoYT	0	0	1
dogpatch626	0	0	1
RotemDoar	0	0	1
Thedoctor1989	0	0	1
timfish	0	0	1
Domdiservice	0	0	1
zloirock	0	0	1
rbuckton	0	0	1
jleedev	0	0	1