Replace dependency rollup-plugin-babel with @rollup/plugin-babel ^5.0.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
rollup-plugin-babel	devDependencies	replacement	^4.0.3 -> ^5.0.0

This is a special PR that replaces rollup-plugin-babel with the community suggested minimal stable replacement version.

---

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - "before 4am on the first day of the month" (UTC).

🚦 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.

[coderabbitai]

Walkthrough

The project has updated its dependency from the deprecated Rollup Babel plugin to the newer @rollup/plugin-babel. This change reflects a transition to a scoped package format, enhancing organization and potentially adopting new features in the build process. The version upgrade signifies a commitment to using modern tools within the JavaScript ecosystem.

Changes

Files	Change Summary
package.json	Updated dependency from "rollup-plugin-babel": "^4.0.3" to "@rollup/plugin-babel": "^5.0.0"

Poem

In the patch of code where rabbits play,
A plugin upgraded, hip-hip-hooray!
With Babel anew, our builds fly high,
Hop, skip, and jump, like clouds in the sky.
A leap in the code, a dance in the light,
Hooray for the change, everything feels right! 🐰✨

---

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.
  • @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 as 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.

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

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)

package.json (1)

61-61: Integration of @rollup/plugin-babel missing in Rollup configuration

The dependency @rollup/plugin-babel has been added to package.json but is not utilized in the rollup.config.js file. To ensure the build process correctly uses this plugin, update the Rollup configuration to include @rollup/plugin-babel.

• File: rollup.config.js
• Action: Add @rollup/plugin-babel to the plugins array in the Rollup configuration.

var babel = require('@rollup/plugin-babel').babel;

module.exports = {
    // ... other configurations
    plugins: [
        babel({ babelHelpers: 'bundled' }),
        // ... other plugins
    ]
};

Analysis chain

Dependency update approved. Verify build process.

The update from rollup-plugin-babel to @rollup/plugin-babel version ^5.0.0 is correct and aligns with modern practices. Ensure that the build process works correctly with this new dependency.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the build process with the updated Babel plugin.

# Test: Run the build script. Expect: Successful build.
npm run build

Length of output: 86

---

Script:

#!/bin/bash
# Check if @rollup/plugin-babel is listed in package.json
rg '@rollup/plugin-babel' package.json

# Find and inspect Rollup configuration files for usage of @rollup/plugin-babel
fd -e js -e mjs -e ts -e json -e cjs -e jsx -e tsx --exec rg '@rollup/plugin-babel' {}

Length of output: 203

---

Script:

#!/bin/bash
# Search for @rollup/plugin-babel in common Rollup configuration files
fd -e js -e mjs -e ts -e json -e cjs -e jsx -e tsx --exec rg '@rollup/plugin-babel' {} | rg 'rollup.config'

Length of output: 107

---

Script:

#!/bin/bash
# Locate rollup.config files and inspect their contents for usage of @rollup/plugin-babel
fd -e js -e mjs -e ts -e json -e cjs -e jsx -e tsx -g 'rollup.config.*' --exec cat {}

Length of output: 853

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c4d32db and 45604ad.

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]

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 45604ad and 2c7c867.

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 (1)

package.json (1)

61-61: Dependency Update Reviewed

The update from "rollup-plugin-babel": "^4.0.3" to "@rollup/plugin-babel": "^5.0.0" is correctly reflected in the devDependencies. This change aligns with modern package management practices by adopting a scoped package name and updating to a newer version.

The dependency update is approved. However, ensure that all references to the old plugin in build scripts or configurations are also updated if necessary.

Run the following script to verify if the old plugin is still referenced anywhere in the project:

Verification successful

---

Dependency Update Verified

The transition from "rollup-plugin-babel": "^4.0.3" to "@rollup/plugin-babel": "^5.0.0" has been successfully completed. No references to the old plugin were found in the codebase, confirming the update is fully integrated.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Search for references to the old `rollup-plugin-babel` in the project files.

# Test: Search for the old plugin name. Expect: No occurrences.
rg --type json --type js 'rollup-plugin-babel'

Length of output: 46

---

Script:

#!/bin/bash
# Description: Perform a comprehensive search for references to the old `rollup-plugin-babel` in all project files.

# Test: Search for the old plugin name across all file types. Expect: No occurrences.
rg 'rollup-plugin-babel'

Length of output: 24