Skip to content

Comments

fix: correctly read split size config#7076

Merged
chenjiahan merged 1 commit intomainfrom
split_by_size_0128
Jan 29, 2026
Merged

fix: correctly read split size config#7076
chenjiahan merged 1 commit intomainfrom
split_by_size_0128

Conversation

@chenjiahan
Copy link
Member

Summary

Updated splitBySize to read minSize and maxSize from config.performance.chunkSplit instead of the removed userConfig property.

Related Links

Checklist

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

Copilot AI review requested due to automatic review settings January 28, 2026 14:18
@chatgpt-codex-connector
Copy link

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@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 refactors the chunk splitting logic within the splitBySize function. It updates the source from which minSize and maxSize configuration values are read, moving from a direct userConfig property to the more structured config.performance.chunkSplit object. This change ensures that the chunk splitting behavior correctly reflects the intended configuration hierarchy and improves the robustness of the build system's performance settings.

Highlights

  • Configuration Access Update: The splitBySize function now correctly retrieves minSize and maxSize properties from config.performance.chunkSplit, aligning with the intended configuration structure.
  • Code Refactoring: The direct dependency on the userConfig property within the splitBySize function has been removed, streamlining the context object destructuring.
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 how splitBySize retrieves its configuration, switching from a userConfig property on the context to using config.performance.chunkSplit. This change aligns with the removal of userConfig. My review includes a suggestion to make the implementation more robust against potential runtime errors.

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.

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

Comments suppressed due to low confidence (1)

packages/core/src/plugins/splitChunks.ts:169

  • The split-by-size strategy lacks test coverage. While the fix correctly reads minSize and maxSize from config.performance.chunkSplit, there are no tests verifying this behavior. Consider adding a test case similar to those in moduleFederation.test.ts that verify the split-by-size strategy works correctly with the legacy performance.chunkSplit configuration.
function splitBySize(ctx: Context): SplitChunks {
  const { override, forceSplittingGroups, config } = ctx;
  const { minSize = 0, maxSize = Number.POSITIVE_INFINITY } = config.performance
    .chunkSplit as SplitBySize;

  return {
    ...getDefaultSplitChunks(config),
    minSize,
    maxSize,
    ...override,
    cacheGroups: {
      ...forceSplittingGroups,
      ...override.cacheGroups,
    },
  };

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

@chenjiahan chenjiahan changed the title fix: split by size config fix: update splitBySize to use performance.chunkSplit config values Jan 28, 2026
@chenjiahan chenjiahan changed the title fix: update splitBySize to use performance.chunkSplit config values fix: correctly read split size config Jan 28, 2026
@chenjiahan chenjiahan merged commit 57deec6 into main Jan 29, 2026
14 checks passed
@chenjiahan chenjiahan deleted the split_by_size_0128 branch January 29, 2026 02:17
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