chore(deps): replace dependency rollup-plugin-terser with @rollup/plugin-terser ^0.1.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
rollup-plugin-terser	devDependencies	replacement	^7.0.2 -> ^0.1.0

This is a special PR that replaces rollup-plugin-terser 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.

[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

The recent changes involve updating the Terser plugin used in a Vue.js application from rollup-plugin-terser to @rollup/plugin-terser. This transition to a scoped version indicates a shift in dependency management, which may impact the JavaScript minification process in production builds.

Changes

Files	Change Summary
.../vue2/package.json	Updated dependency from "rollup-plugin-terser": "^7.0.2" to "@rollup/plugin-terser": "^0.1.0"

Poem

🐇 In the garden of code, a change takes flight,
Terser now scoped, shining so bright.
With rolls of the plugin, minify we shall,
Making our builds smooth, oh what a ball!
Hopping through updates, we dance in delight,
For every small tweak brings joy to our sight. 🎉

---

🪧 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/vue2/package.json (1)

51-51: Integration Issue Found:

The rollup configuration file (apps/vue2/rollup.config.js) still imports rollup-plugin-terser. The new dependency @rollup/plugin-terser has not been integrated into the codebase.

• File: apps/vue2/rollup.config.js
  • Line: import {terser} from 'rollup-plugin-terser';

Please update the rollup configuration to use @rollup/plugin-terser instead of rollup-plugin-terser.

Analysis chain

LGTM! Verify the compatibility of the new dependency.

The dependency update from rollup-plugin-terser to @rollup/plugin-terser is approved.

However, ensure that the new package version ^0.1.0 is compatible with the existing build process.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the compatibility of `@rollup/plugin-terser` with the existing build process.

# Test: Check if `@rollup/plugin-terser` is used in the rollup configuration files.
# Expect: No errors or issues in the build process.

# Search for the usage of `@rollup/plugin-terser` in rollup configuration files.
rg --type js '@rollup/plugin-terser'

# Check if the build process runs successfully.
npm run build

Length of output: 124

---

Script:

#!/bin/bash
# Description: Verify the usage of `@rollup/plugin-terser` and `rollup-plugin-terser` in the rollup configuration files.

# Search for the usage of `@rollup/plugin-terser` in rollup configuration files.
rg --type js '@rollup/plugin-terser'

# Search for the usage of `rollup-plugin-terser` in rollup configuration files.
rg --type js 'rollup-plugin-terser'

Length of output: 144

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6c1eae2 and eb0dfb0.

Files ignored due to path filters (1)

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

Files selected for processing (2)

• apps/vue2/package.json (1 hunks)
• components/vue2/package.json (1 hunks)

Files skipped from review due to trivial changes (1)

• components/vue2/package.json

[coderabbitai]

Actionable comments posted: 0

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

components/vue2/package.json (1)

127-127: Dependency Update Required: Integrate @rollup/plugin-terser in Build Configuration

The rollup-plugin-terser is still being used in apps/vue2/rollup.config.js, and there is no reference to @rollup/plugin-terser. Please update the build configuration to use the new plugin to ensure compatibility with the build process.

• apps/vue2/rollup.config.js: Replace import {terser} from 'rollup-plugin-terser'; with the appropriate import for @rollup/plugin-terser.

Analysis chain

Dependency Update: Ensure compatibility with the build process.

The dependency rollup-plugin-terser has been replaced with @rollup/plugin-terser. Verify that the new plugin is compatible with the existing build configuration and that there are no breaking changes in the minification process.

Run the following script to check for the usage of the old plugin and ensure that the new plugin is correctly integrated:

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the old and new Terser plugins in the build configuration.

# Test: Search for the old plugin usage. Expect: No occurrences of `rollup-plugin-terser`.
rg --type js 'rollup-plugin-terser'

# Test: Search for the new plugin usage. Expect: Occurrences of `@rollup/plugin-terser`.
rg --type js '@rollup/plugin-terser'

Length of output: 144

---

Script:

#!/bin/bash
# Description: Check the rollup configuration for references to the new and old Terser plugins.

# Search for any configuration related to the new Terser plugin in rollup.config.js
rg '@rollup/plugin-terser' apps/vue2/rollup.config.js -A 5

# Search for any configuration related to the old Terser plugin in rollup.config.js
rg 'rollup-plugin-terser' apps/vue2/rollup.config.js -A 5

Length of output: 270

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between eb0dfb0 and b551328.

Files ignored due to path filters (1)

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

Files selected for processing (2)

• apps/vue2/package.json (1 hunks)
• components/vue2/package.json (1 hunks)

Additional comments not posted (1)

apps/vue2/package.json (1)

51-51: Dependency Update: Ensure compatibility with the build process.

The dependency rollup-plugin-terser has been replaced with @rollup/plugin-terser. Verify that the new plugin is compatible with the existing build configuration and that there are no breaking changes in the minification process.

Run the following script to check for the usage of the old plugin and ensure that the new plugin is correctly integrated: