feat: use address@2

[fengmk2]

Summary by CodeRabbit

• Chores

  • Updated Node.js versions in CI configuration to include newer versions.
  • Updated dependencies in package.json to newer versions and specified a minimum Node.js version.

• Refactor

  • Replaced debug logging mechanism with util.debuglog in specific utility files for improved performance.

• Tests

  • Changed the assertion library from power-assert to assert in test files for consistency.

• Documentation

  • Updated timestamp in the README.md file to reflect the latest changes.

[coderabbitai]

Important

Auto Review Skipped

Auto reviews are disabled on base/target branches other than the default branch. Please add the base/target branch pattern to the list of additional branches to be reviewed in the settings.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This update focuses on modernizing the project's Node.js environment, refining debugging methods, and updating dependency versions. Key changes include expanding Node.js version support, switching from debug to util.debuglog for internal logging, and updating the assertion library in tests. The update also removes the 'use strict'; directive in multiple files, reflecting a shift towards more modern JavaScript practices.

Changes

File Path	Change Summary
.eslintrc.js, bin/detect-port.js, test/cli.test.js, test/wait-port.test.js	Removed 'use strict'; directive
.github/workflows/...	Updated Node.js versions and paths in CI/CD workflows
lib/detect-port.js, lib/wait-port.js	Replaced debug with util.debuglog for logging
test/detect-port.test.js	Switched from power-assert to assert module
package.json	Updated dependencies and specified minimum Node.js version
README.md	Updated timestamp in auto-update section

🐰✨
O hark! A change, a shift, a tweak,
In code where rabbits dare not speak.
From strict to loose, the scripts now leap,
With logs that whisper secrets deep.
Rejoice in updates, fresh and sleek! 🌟
🐰✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/address@2.0.2	environment	0	62.3 kB	fengmk2
npm/egg-bin@6.8.1	environment Transitive: eval, filesystem, network, shell, unsafe	+272	56.8 MB	fengmk2
npm/git-contributor@2.1.5	environment, shell Transitive: eval, filesystem, network, unsafe	+85	8.95 MB	xudafeng
npm/mm@3.4.0	network, shell	+7	97.9 kB	fengmk2

🚮 Removed packages: npm/egg-bin@5.18.1, npm/git-contributor@1.1.0, npm/mm@2.5.0, npm/power-assert@1.6.1

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/egg-bin@6.8.1

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[fengmk2]

@SocketSecurity ignore npm/egg-bin@6.8.1

[coderabbitai]

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9804ad5 and 0a1c569.

Files selected for processing (11)

• .eslintrc.js (1 hunks)
• .github/workflows/nodejs.yml (1 hunks)
• .github/workflows/release.yml (1 hunks)
• README.md (1 hunks)
• bin/detect-port.js (1 hunks)
• lib/detect-port.js (1 hunks)
• lib/wait-port.js (1 hunks)
• package.json (1 hunks)
• test/cli.test.js (1 hunks)
• test/detect-port.test.js (1 hunks)
• test/wait-port.test.js (1 hunks)

Files skipped from review due to trivial changes (5)

• .eslintrc.js
• bin/detect-port.js
• test/cli.test.js
• test/detect-port.test.js
• test/wait-port.test.js

Additional Context Used

LanguageTool (14)

README.md (14)

Near line 25: Unpaired symbol: ‘]’ seems to be missing
Context: ...tor ## Who are using or has used - ⭐⭐⭐eggjs/egg - ⭐⭐⭐...

---

Near line 26: Unpaired symbol: ‘]’ seems to be missing
Context: ...eggjs/egg](//github.com/eggjs/egg) - ⭐⭐⭐alibaba/ice -...

---

Near line 27: Unpaired symbol: ‘]’ seems to be missing
Context: ...aba/ice](//github.com/alibaba/ice) - ⭐⭐⭐[alibaba/uirecorder](//github.com/alibaba...

---

Near line 28: Unpaired symbol: ‘]’ seems to be missing
Context: ...](//github.com/alibaba/uirecorder) - ⭐⭐⭐[facebook/create-react-app](//github.com/...

---

Near line 29: Unpaired symbol: ‘]’ seems to be missing
Context: ...ages/react-dev-utils/package.json) - ⭐⭐⭐[facebook/flipper](//github.com/facebook/...

---

Near line 30: Unpaired symbol: ‘]’ seems to be missing
Context: ...er](//github.com/facebook/flipper) - ⭐⭐⭐umijs/umi - ⭐⭐⭐...

---

Near line 31: Unpaired symbol: ‘]’ seems to be missing
Context: ...umijs/umi](//github.com/umijs/umi) - ⭐⭐⭐[gatsbyjs/gatsby](//github.com/gatsbyjs/g...

---

Near line 32: Unpaired symbol: ‘]’ seems to be missing
Context: ...sby](//github.com/gatsbyjs/gatsby) - ⭐⭐⭐[electron-react-boilerplate/electron-reac...

---

Near line 33: Unpaired symbol: ‘]’ seems to be missing
Context: ...rplate/electron-react-boilerplate) - ⭐⭐⭐zeit/micro - ⭐...

---

Near line 34: Unpaired symbol: ‘]’ seems to be missing
Context: ...it/micro](//github.com/zeit/micro) - ⭐⭐⭐[rails/webpacker](//github.com/rails/webp...

---

Near line 35: Unpaired symbol: ‘]’ seems to be missing
Context: ...ker](//github.com/rails/webpacker) - ⭐⭐⭐[storybookjs/storybook](//github.com/stor...

---

Near line 103: Unpaired symbol: ‘]’ seems to be missing
Context: ...b>](https://github.com/yavuzakyuz)
|[<img src="https://avatars.githubusercont...

---

Near line 105: It appears that a hyphen is missing (if ‘auto’ is not used in the context of ‘cars’).
Context: ...//github.com/xudafeng/git-contributor), auto updated at Wed May 08 2024 15:54:54 GMT+0800....

---

Near line 105: Commas set off the year in a month-day-year date.
Context: ...afeng/git-contributor), auto updated at Wed May 08 2024 15:54:54 GMT+0800. <!-- GITCONTR...

Additional comments not posted (8)

.github/workflows/release.yml (1)

10-10: Ensure the new GitHub Actions workflow path is correct and accessible.

Verification successful

---

The verification script successfully confirmed the existence and accessibility of the repository node-modules/github-actions on the master branch. The output provided detailed information about the repository, including descriptions of its functionalities such as unit testing, automatic package publishing, and repository configuration initialization. It also included examples of workflow configurations that utilize this repository, confirming that the repository is structured to support such workflows.

Given this information, the updated GitHub Actions workflow path specified in the .github/workflows/release.yml file is correct and accessible. The repository not only exists but also contains relevant workflows that can be referenced, as demonstrated in the provided examples.

Therefore, the change made in the .github/workflows/release.yml file is verified to be correct.

---

GitHub Actions Workflow Path Verified

The new GitHub Actions workflow path specified in the .github/workflows/release.yml file has been confirmed to be correct and accessible. The repository node-modules/github-actions on the master branch contains the necessary workflows and supports the functionalities described.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Verify the existence and accessibility of the GitHub Actions workflow in the new repository and branch.

# Test: Check if the repository and branch exist.
gh repo view node-modules/github-actions --branch master

Length of output: 3616

.github/workflows/nodejs.yml (2)

12-12: Ensure the new GitHub Actions workflow path is correct and accessible.

Verification successful

---

The verification script successfully confirmed the existence and accessibility of the node-modules/github-actions repository on the master branch. The output provided detailed information about the repository, including its description and some specific workflows used within it, such as node-test.yml and node-test-mysql.yml, both referenced with the master branch.

This confirms that the updated uses path in the .github/workflows/nodejs.yml file is correct and points to an existing and accessible workflow in the node-modules/github-actions repository. Therefore, the change made in the pull request is verified as correct.

Final Response:

The updated GitHub Actions workflow path in .github/workflows/nodejs.yml is verified as correct and accessible. The repository node-modules/github-actions on the master branch contains the referenced workflow file.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Verify the existence and accessibility of the GitHub Actions workflow in the new repository and branch.

# Test: Check if the repository and branch exist.
gh repo view node-modules/github-actions --branch master

Length of output: 3616

---

15-15: Adding Node.js versions 20 and 22 to the testing matrix is a good practice to ensure compatibility with newer versions.

lib/wait-port.js (1)

1-1: Switching to util.debuglog for debugging is a good practice to reduce external dependencies.

package.json (2)

24-33: Ensure that the updated dependencies are compatible with the new minimum Node.js version requirement.

---

42-42: Specifying a minimum Node.js version of 14.0.0 is a good practice to ensure compatibility with newer environments.

lib/detect-port.js (1)

2-2: Switching to util.debuglog for debugging is a good practice to reduce external dependencies.

README.md (1)

105-105: Ensure the timestamp format is consistent with the rest of the document.