chore(deps): replace dependency npm-run-all with npm-run-all2 ^5.0.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
npm-run-all	devDependencies	replacement	^4.1.5 -> ^5.0.0

This is a special PR that replaces npm-run-all with the community suggested minimal stable replacement version.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sweep-nightly]

Apply Sweep Rules to your PR?

• Apply: All new business logic should have corresponding unit tests.
• Apply: Refactor large functions to be more modular.
• Apply: Add docstrings to all functions and file headers.

[coderabbitai]

Important

Review skipped

Bot user detected.

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

In this update, the Vue.js application has transitioned from using the npm-run-all package to a new package named npm-run-all2. The version has been upgraded from ^4.1.5 to ^5.0.0, indicating a shift that may enhance the application's task execution capabilities. The new package likely introduces different features or improvements, although the specific implications depend on its characteristics.

Changes

File	Change Summary
apps/vue3/package.json	Updated dependency from "npm-run-all": "^4.1.5" to "npm-run-all2": "^5.0.0"

Poem

🐇 In the garden of code, I hop with glee,
A new package blooms, so fresh and free!
From npm-run-all, we take a leap,
To npm-run-all2, our tasks to keep.
With every upgrade, our builds take flight,
Hopping along, everything feels just right! 🌼✨

---

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

[coderabbitai]

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (1)

apps/vue3/package.json (1)

34-34: npm-run-all2 is not used in the codebase.

The package npm-run-all2 is not referenced in any scripts or other parts of the codebase, suggesting it is an unnecessary dependency.

• apps/vue3/package.json: Line 34
• pnpm-lock.yaml

Analysis chain

Verify compatibility and functionality of npm-run-all2.

Ensure that npm-run-all2 is compatible with the existing scripts (run-p commands) and provides the same or improved functionality compared to npm-run-all.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that `npm-run-all2` is compatible with the existing scripts.

# Test: Check if `npm-run-all2` provides the `run-p` command and other required functionalities.
npm info npm-run-all2

Length of output: 94

---

Script:

#!/bin/bash
# Description: Search for usage of `npm-run-all` or `npm-run-all2` in the `package.json` file.

# Locate the package.json file in the apps/vue3 directory
fd package.json apps/vue3 --exec cat {} | grep -E '"run-p"|"npm-run-all"|"npm-run-all2"'

Length of output: 122

---

Script:

#!/bin/bash
# Description: Search for usage of `npm-run-all2` across the entire codebase.

# Search for any references to `npm-run-all2` in the codebase
rg "npm-run-all2"

Length of output: 143

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b42c6db and 3c70e88.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

• apps/vue3/package.json (1 hunks)

[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 3c70e88 and f37d028.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

• apps/vue3/package.json (1 hunks)

Additional comments not posted (1)

apps/vue3/package.json (1)

34-34: Dependency Update Reviewed: npm-run-all2

The update from "npm-run-all": "^4.1.5" to "npm-run-all2": "^5.0.0" is correctly reflected in the devDependencies. This change aligns with the PR's objective to transition to a newer version of the package, potentially offering more stability or features.

The dependency update is approved.

It's crucial to ensure that npm-run-all2 is compatible with the existing project setup and that all scripts previously using npm-run-all are updated or verified to work with the new package. This verification is essential to prevent any disruptions in the build or development processes.

Verification successful

---

No Script References to npm-run-all Found

The package.json file does not contain any script references to npm-run-all, indicating that the update to npm-run-all2 does not disrupt existing scripts. However, it's recommended to manually verify the functionality of npm-run-all2 within the project to ensure full compatibility and prevent any potential issues.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify if any scripts explicitly reference the old `npm-run-all` package.

# Test: Search for the old package name in the scripts section. Expect: No occurrences.
rg --type json -A 2 $'npm-run-all' apps/vue3/package.json

Length of output: 140