feat: upgrade deps

[fengmk2]

BREAKING CHANGE: drop Node.js < 14 support

Summary by CodeRabbit

• New Features
  • Introduced a new GitHub Actions workflow for Node.js releases.
• Enhancements
  • Updated continuous integration workflow with improved job configurations.
  • Enhanced file system operations across multiple JavaScript files using Node.js built-in modules.
• Bug Fixes
  • Fixed directory and file operations in test suites to use updated Node.js methods.
• Documentation
  • Adjusted documentation comments and removed outdated directives.
• Refactor
  • Removed the use of 'use strict'; in several JavaScript files to align with modern standards.
• Dependencies
  • Updated various dependencies and Node version requirements to ensure compatibility and security.

[coderabbitai]

Walkthrough

The changes encompass modernizing the codebase by migrating to built-in Node.js modules for path and file system operations, adjusting GitHub workflows, and removing 'use strict'; directives across files to align with newer JavaScript standards.

Changes

File Pattern	Summary of Changes
.github/workflows/nodejs.yml, release.yml	Workflow restructuring, introduction of release.yml for Node.js releases.
agent.js, app.js, app/middleware/..., config/config.default.js, test/...	Transitioned from deprecated modules to node:fs/promises and node:path.
package.json	Dependency updates, Node.js version requirement adjustment, script modifications.

🐰🌟
In the garden of code, where changes bloom bright,
A rabbit hopped through files, with delight in its sight.
Old modules bid adieu, as new paths were found,
The code sang a tune, with freshness all around.
With each leap and bound, a story unfurled,
Of a codebase transformed, in a changing world. 🌼📜
🐰🌟

---

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/[email protected]	environment Transitive: eval, filesystem, network, shell, unsafe	+267	56.7 MB	fengmk2
npm/[email protected]	environment, filesystem, network, shell Transitive: eval, unsafe	+192	13 MB	fengmk2
npm/[email protected]	filesystem, network, unsafe Transitive: environment, eval, shell	+291	20 MB	fengmk2
npm/[email protected]	Transitive: environment, eval, filesystem, unsafe	+248	68.6 MB	fengmk2
npm/[email protected]	environment, filesystem Transitive: eval, shell, unsafe	+88	10.5 MB	eslintbot
npm/[email protected]	None	+6	43.3 kB	sindresorhus
npm/[email protected]	None	+4	194 kB	fengmk2

🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

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/[email protected]

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

[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 011a3ce and 2e0869c.

Files selected for processing (16)

• .github/workflows/nodejs.yml (1 hunks)
• .github/workflows/release.yml (1 hunks)
• agent.js (2 hunks)
• app.js (1 hunks)
• app/middleware/egg_loader_trace.js (2 hunks)
• config/config.default.js (1 hunks)
• package.json (1 hunks)
• test/absolute.test.js (2 hunks)
• test/custom.test.js (1 hunks)
• test/development.test.js (1 hunks)
• test/fast_ready_false.test.js (1 hunks)
• test/not-reload.test.js (1 hunks)
• test/override.test.js (1 hunks)
• test/process_mode_single.test.js (1 hunks)
• test/timing.test.js (1 hunks)
• test/utils.js (1 hunks)

Files skipped from review due to trivial changes (3)

• .github/workflows/release.yml
• config/config.default.js
• test/utils.js

Additional comments not posted (22)

.github/workflows/nodejs.yml (2)

1-1: Renaming the workflow to "CI" clarifies its purpose.

---

11-16: Ensure the new job configuration is correctly set up for multiple Node.js versions.

test/not-reload.test.js (1)

1-3: Transition to native Node.js modules enhances maintainability and future-proofing.

test/fast_ready_false.test.js (1)

1-1: Using native Node.js timer promises improves the readability and efficiency of asynchronous operations.

test/custom.test.js (1)

1-3: Adopting native Node.js modules for file and path operations is a positive change.

app/middleware/egg_loader_trace.js (2)

1-2: Switching to native Node.js modules for path and file operations is a good practice.

---

20-20: Ensure that the readJSON function is correctly imported and used here.

Verification successful

---

The readJSON function is correctly imported from the 'utility' module and used in app/middleware/egg_loader_trace.js as expected. This confirms the proper implementation as per the review comment.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Verify the usage of `readJSON` function.

# Test: Search for the import and usage of `readJSON`.
rg --type js 'readJSON'

Length of output: 192

test/absolute.test.js (3)

1-3: Using native Node.js modules for asynchronous operations and file handling is a commendable update.

---

9-13: Correct use of native Node.js methods for file system operations enhances code efficiency.

---

30-30: Good practice to ensure directories exist before writing files.

package.json (4)

22-23: Updated dependency versions to align with the new Node.js version requirements.

---

26-30: Updated development dependencies reflect the project's alignment with newer standards.

---

34-34: Setting the Node.js version requirement to >=14.0.0 is consistent with the PR's objectives.

---

37-41: Modifications to the scripts ensure compatibility with the updated Node.js version and dependencies.

test/process_mode_single.test.js (2)

1-4: Switch to native Node.js modules for better maintainability and performance.

---

4-4: Ensure that the sleep function from node:timers/promises is used correctly across the test cases.

Verification successful

---

The revised script using the --pcre2 flag did not find any instances of incorrect usage patterns for the sleep function in test/process_mode_single.test.js. This indicates that the sleep function is being used correctly with the specified durations (1000, 2000, or 5000 milliseconds) in the test cases.

Correct usage of sleep function verified in test cases.

• No instances of incorrect usage patterns were found in test/process_mode_single.test.js.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Verify correct usage of `sleep` function in `test/process_mode_single.test.js`.

# Test: Search for incorrect usage patterns of `sleep`. Expect: No occurrences of incorrect patterns.
rg --type js "sleep\((?!1000|2000|5000)\d+\)" test/process_mode_single.test.js

Length of output: 321

---

---

Script:

#!/bin/bash
# Description: Verify correct usage of `sleep` function in `test/process_mode_single.test.js` using PCRE2 for advanced regex features.

# Test: Search for incorrect usage patterns of `sleep`. Expect: No occurrences of incorrect patterns.
rg --type js --pcre2 "sleep\((?!1000|2000|5000)\d+\)" test/process_mode_single.test.js

Length of output: 88

test/timing.test.js (2)

1-4: Adoption of native Node.js modules enhances compatibility with the latest Node.js versions.

---

12-12: Proper use of filesystem operations to ensure the setup of test environment.

test/development.test.js (1)

1-4: Transition to native Node.js modules is consistent with modern Node.js practices.

test/override.test.js (1)

1-3: Use of native Node.js modules for filesystem and timing operations aligns with the updated Node.js version requirements.

agent.js (2)

1-2: Updated to use native Node.js modules for path and filesystem operations, enhancing compatibility and performance.

---

13-13: Correct use of fs.rm with options to ensure robust file removal in the agent's runtime directory.

[fengmk2]

@SocketSecurity ignore npm/[email protected]

[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 2e0869c and 78603bf.

Files selected for processing (9)

• test/absolute.test.js (2 hunks)
• test/custom.test.js (1 hunks)
• test/development.test.js (1 hunks)
• test/fast_ready_false.test.js (1 hunks)
• test/not-reload.test.js (1 hunks)
• test/override.test.js (1 hunks)
• test/process_mode_single.test.js (1 hunks)
• test/timing.test.js (3 hunks)
• test/utils.js (1 hunks)

Files skipped from review as they are similar to previous changes (8)

• test/custom.test.js
• test/development.test.js
• test/fast_ready_false.test.js
• test/not-reload.test.js
• test/override.test.js
• test/process_mode_single.test.js
• test/timing.test.js
• test/utils.js

Additional comments not posted (3)

test/absolute.test.js (3)

1-4: The updated import statements using native Node.js modules are correctly implemented.

---

9-13: The replacement of rimraf and mkdirp with fs.rm and fs.mkdir using native promises is correctly implemented. Ensure the behavior of these operations matches the expected outcomes in all test scenarios.

---

30-30: The use of native fs methods for file operations in the test is correctly implemented. Consider reviewing the use of sleep(5000) to avoid potential flakiness in tests.