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.0 -> ^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 becomes conflicted, 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.

Summary by CodeRabbit

• Chores
  • Updated internal build tooling dependencies to modern standards, enhancing build stability and overall performance.
  • This maintenance update refines our development process and aligns our environment with current best practices, supporting long-term reliability.
  • End-users may notice subtle performance improvements as a result, although no direct user-facing features have been changed.

[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 project has transitioned from using rollup-plugin-terser to @rollup/plugin-terser in the package.json file. This change includes an update in the versioning from ^7.0.0 to ^0.1.0, reflecting a shift to a scoped package that may involve differences in implementation and compatibility with Rollup or Svelte.

Changes

File	Change Summary
package.json	Replaced "rollup-plugin-terser": "^7.0.0" with "@rollup/plugin-terser": "^0.1.0"

Poem

In a patch of code where bunnies play,
A new plugin hops in to save the day.
Terser now scoped, oh what a delight,
Optimizations dance in the moonlight.
With every change, our builds will gleam,
Hopping along, we chase the dream! 🐇✨

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Join our Discord community for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this 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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 40faa2d and 5d69a1e.

Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

Files selected for processing (1)

• package.json (1 hunks)

Additional comments not posted (2)

package.json (2)

21-21: Verify version number for @rollup/plugin-terser.

The version ^0.1.0 seems unusually low for a replacement of rollup-plugin-terser which was at ^7.0.0. This could be a major version downgrade or a reset in version numbering due to the rebranding under a scoped package. Please confirm that this version is correct and that it contains all necessary features and compatibility with the current Rollup version used in the project (^3.0.0).

---

21-21: Ensure compatibility with existing Rollup configuration and plugins.

Given the significant version change, it's crucial to ensure that @rollup/plugin-terser integrates well with the existing Rollup version (^3.0.0) and other plugins like rollup-plugin-svelte (^7.0.0). Review the plugin's documentation for any breaking changes or new configurations required.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5d69a1e and 8711c01.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• package.json (1 hunks)

[coderabbitai]

💡 Verification agent

🧩 Analysis chain

Dependency Update: Verify Compatibility of New Terser Plugin

The dependency update to "@rollup/plugin-terser": "^0.1.0" replaces the older "rollup-plugin-terser": "^7.0.0". Please ensure that the Rollup configuration is updated accordingly, as the API for the new plugin might differ from the old one. It is recommended to verify that all build configurations and any custom terser options are still valid with the new dependency.

---

Please run the above script to verify that:

• All references to "rollup-plugin-terser" have been removed.
• The new dependency "@rollup/plugin-terser" is in use in both the package configuration and any relevant Rollup config files.

Once you confirm these checks, we can safely conclude that the updated dependency is implemented correctly.

---

🏁 Script executed:

#!/bin/bash
echo "Verifying dependency updates in the codebase..."

echo -e "\nSearching for references to the old dependency 'rollup-plugin-terser':"
rg "rollup-plugin-terser" .

echo -e "\nSearching for references to the new dependency '@rollup/plugin-terser':"
rg "@rollup/plugin-terser" .

Length of output: 1035

---

Action Required: Update Rollup Configuration for New Terser Plugin

The new dependency "@rollup/plugin-terser": "^0.1.0" has been added to package.json and is correctly reflected in yarn.lock. However, our search revealed that references to the old dependency (rollup-plugin-terser) still exist in the codebase:

• In rollup.config.js, the code still imports terser as follows:

  import { terser } from 'rollup-plugin-terser';

• In scripts/setupTypeScript.js, there is a reference that manipulates the old dependency string.

Next Steps:

• Update rollup.config.js to import terser from "@rollup/plugin-terser", adapting any API changes if necessary.
• Revise scripts/setupTypeScript.js to remove or update references to "rollup-plugin-terser" in favor of the new plugin.

Please ensure that all build configurations and custom terser options are compatible with the new dependency.