Skip to content

Comments

fix: update chunk name for per-package preset#7102

Merged
chenjiahan merged 3 commits intomainfrom
split_chunks_per_pkg_0131
Feb 1, 2026
Merged

fix: update chunk name for per-package preset#7102
chenjiahan merged 3 commits intomainfrom
split_chunks_per_pkg_0131

Conversation

@chenjiahan
Copy link
Member

Summary

Changed the output chunk naming format in per-package preset from npm.react to npm-react (and for scoped packages, from e.g. npm.babel.runtime to npm-babel_runtime).

Checklist

  • Tests updated (or not required).
  • Documentation updated (or not required).

Copilot AI review requested due to automatic review settings January 31, 2026 13:27
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @chenjiahan, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the chunk naming strategy for the per-package split chunks preset. The change aims to standardize the output chunk names, moving from a dot-separated format to a hyphen-separated one, and handling scoped packages with underscores, ensuring consistency and potentially improving compatibility with various file systems or tools.

Highlights

  • Chunk Naming Convention Update: The naming format for output chunks in the per-package preset has been changed from npm.package to npm-package.
  • Scoped Package Naming: For scoped packages, the format npm.scope.package is now npm-scope_package, replacing dots with hyphens and underscores.
  • Test Updates: End-to-end tests have been adjusted to assert the new chunk naming convention.
  • Documentation Refresh: Both English and Chinese documentation for the per-package split chunks preset have been updated to reflect the new chunk naming examples.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the chunk naming format for the per-package preset to use hyphens and underscores instead of dots, which improves readability. The implementation is correct, and the e2e tests and documentation have been updated accordingly. However, I've noticed that the unit tests for the modified getPackageNameFromModulePath function were not updated, which could lead to test failures. I've left a comment with a suggestion to fix this.

@cloudflare-workers-and-pages
Copy link

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0c6c264dce

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the chunk naming format for the per-package preset from dot-separated names (e.g., npm.react, npm.babel.runtime) to hyphen/underscore-separated names (e.g., npm-react, npm-babel_runtime).

Changes:

  • Modified getPackageNameFromModulePath function to generate chunk names with hyphens and underscores instead of dots
  • Updated E2E tests to expect the new naming format
  • Enhanced documentation to include examples of the new chunk names

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
packages/core/src/plugins/splitChunks.ts Simplified the chunk name generation logic to use template literals with hyphen/underscore separators
e2e/cases/split-chunks/preset-per-package/index.test.ts Updated test assertions to check for the new hyphen-based naming format
e2e/cases/split-chunks/legacy-by-module/index.test.ts Updated test assertions to check for the new hyphen-based naming format
website/docs/en/config/split-chunks.mdx Added examples showing the new chunk naming format (npm-react.js, npm-babel_runtime.js)
website/docs/zh/config/split-chunks.mdx Added examples showing the new chunk naming format (npm-react.js, npm-babel_runtime.js)

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@chenjiahan chenjiahan merged commit 797fd9d into main Feb 1, 2026
5 checks passed
@chenjiahan chenjiahan deleted the split_chunks_per_pkg_0131 branch February 1, 2026 00:43
@chenjiahan chenjiahan mentioned this pull request Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant