Skip to content

fix: disable unbundle#350

Merged
fengmk2 merged 1 commit intonextfrom
disable-unbundle
Oct 4, 2025
Merged

fix: disable unbundle#350
fengmk2 merged 1 commit intonextfrom
disable-unbundle

Conversation

@fengmk2
Copy link
Member

@fengmk2 fengmk2 commented Oct 4, 2025

@fengmk2 fengmk2 requested a review from Copilot October 4, 2025 15:49
Copy link

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 disables the unbundle configuration option across all tsdown config files in the project. The change comments out the unbundle: true setting in 35 configuration files to modify the build behavior from unbundled to bundled output.

  • Systematically commented out unbundle: true in all tsdown configuration files
  • Affects both core and plugin modules to ensure consistent build configuration
  • References an upstream issue in the eggjs/egg repository for context

Reviewed Changes

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

Show a summary per file
File Description
standalone/standalone/tsdown.config.ts Disabled unbundle option for standalone module
plugin/tegg/tsdown.config.ts Disabled unbundle option for tegg plugin
plugin/schedule/tsdown.config.ts Disabled unbundle option for schedule plugin
plugin/orm/tsdown.config.ts Disabled unbundle option for orm plugin
plugin/eventbus/tsdown.config.ts Disabled unbundle option for eventbus plugin
plugin/dal/tsdown.config.ts Disabled unbundle option for dal plugin
plugin/controller/tsdown.config.ts Disabled unbundle option for controller plugin
plugin/config/tsdown.config.ts Disabled unbundle option for config plugin
plugin/common/tsdown.config.ts Disabled unbundle option for common plugin
plugin/aop/tsdown.config.ts Disabled unbundle option for aop plugin
plugin/ajv/tsdown.config.ts Disabled unbundle option for ajv plugin
core/types/tsdown.config.ts Disabled unbundle option for types core module
core/transaction-decorator/tsdown.config.ts Disabled unbundle option for transaction-decorator core module
core/test-util/tsdown.config.ts Disabled unbundle option for test-util core module
core/tegg/tsdown.config.ts Disabled unbundle option for tegg core module
core/standalone-decorator/tsdown.config.ts Disabled unbundle option for standalone-decorator core module
core/schedule-decorator/tsdown.config.ts Disabled unbundle option for schedule-decorator core module
core/runtime/tsdown.config.ts Disabled unbundle option for runtime core module
core/orm-decorator/tsdown.config.ts Disabled unbundle option for orm-decorator core module
core/metadata/tsdown.config.ts Disabled unbundle option for metadata core module
core/loader/tsdown.config.ts Disabled unbundle option for loader core module
core/lifecycle/tsdown.config.ts Disabled unbundle option for lifecycle core module
core/eventbus-runtime/tsdown.config.ts Disabled unbundle option for eventbus-runtime core module
core/eventbus-decorator/tsdown.config.ts Disabled unbundle option for eventbus-decorator core module
core/dynamic-inject/tsdown.config.ts Disabled unbundle option for dynamic-inject core module
core/dynamic-inject-runtime/tsdown.config.ts Disabled unbundle option for dynamic-inject-runtime core module
core/dal-runtime/tsdown.config.ts Disabled unbundle option for dal-runtime core module
core/dal-decorator/tsdown.config.ts Disabled unbundle option for dal-decorator core module
core/core-decorator/tsdown.config.ts Disabled unbundle option for core-decorator core module
core/controller-decorator/tsdown.config.ts Disabled unbundle option for controller-decorator core module
core/common-util/tsdown.config.ts Disabled unbundle option for common-util core module
core/background-task/tsdown.config.ts Disabled unbundle option for background-task core module
core/aop-runtime/tsdown.config.ts Disabled unbundle option for aop-runtime core module
core/aop-decorator/tsdown.config.ts Disabled unbundle option for aop-decorator core module
core/ajv-decorator/tsdown.config.ts Disabled unbundle option for ajv-decorator core module

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@coderabbitai
Copy link

coderabbitai bot commented Oct 4, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. 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.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch disable-unbundle

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @fengmk2, 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 systematically disables the 'unbundle' configuration option within the tsdown.config.ts files across a wide range of core and plugin modules. The primary purpose of this change is to modify the build process, likely to prevent unbundling or to align with a new bundling strategy, ensuring consistent behavior across the affected components.

Highlights

  • Configuration Change: The unbundle: true configuration option has been commented out in all tsdown.config.ts files across various core modules and plugins.
  • Scope of Change: This modification affects numerous modules, including ajv-decorator, aop-decorator, aop-runtime, background-task, common-util, controller-decorator, core-decorator, dal-decorator, dal-runtime, dynamic-inject-runtime, dynamic-inject, eventbus-decorator, eventbus-runtime, lifecycle, loader, metadata, orm-decorator, runtime, schedule-decorator, standalone-decorator, tegg, test-util, transaction-decorator, types, and several plugin/ modules.
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 disables the unbundle option in tsdown.config.ts for multiple packages by commenting out the unbundle: true line. While this achieves the goal, a cleaner approach for maintainability would be to remove the line entirely instead of commenting it out. This avoids clutter and potential confusion from stale code in the configuration files. I've added specific suggestions to each affected file to remove the commented line.

'src/index.ts',
],
unbundle: true,
// unbundle: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability, it's preferable to remove this line entirely rather than commenting it out. If the goal is to use the default value for unbundle (which is likely false), removing the line makes the configuration cleaner and avoids potential confusion from stale commented-out code.

'src/index.ts',
],
unbundle: true,
// unbundle: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability, it's preferable to remove this line entirely rather than commenting it out. If the goal is to use the default value for unbundle (which is likely false), removing the line makes the configuration cleaner and avoids potential confusion from stale commented-out code.

'src/index.ts',
],
unbundle: true,
// unbundle: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability, it's preferable to remove this line entirely rather than commenting it out. If the goal is to use the default value for unbundle (which is likely false), removing the line makes the configuration cleaner and avoids potential confusion from stale commented-out code.

'src/index.ts',
],
unbundle: true,
// unbundle: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability, it's preferable to remove this line entirely rather than commenting it out. If the goal is to use the default value for unbundle (which is likely false), removing the line makes the configuration cleaner and avoids potential confusion from stale commented-out code.

'src/index.ts',
],
unbundle: true,
// unbundle: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability, it's preferable to remove this line entirely rather than commenting it out. If the goal is to use the default value for unbundle (which is likely false), removing the line makes the configuration cleaner and avoids potential confusion from stale commented-out code.

export default defineConfig({
entry: 'src/**/*.ts',
unbundle: true,
// unbundle: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability, it's preferable to remove this line entirely rather than commenting it out. If the goal is to use the default value for unbundle (which is likely false), removing the line makes the configuration cleaner and avoids potential confusion from stale commented-out code.

export default defineConfig({
entry: 'src/**/*.ts',
unbundle: true,
// unbundle: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability, it's preferable to remove this line entirely rather than commenting it out. If the goal is to use the default value for unbundle (which is likely false), removing the line makes the configuration cleaner and avoids potential confusion from stale commented-out code.

export default defineConfig({
entry: 'src/**/*.ts',
unbundle: true,
// unbundle: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability, it's preferable to remove this line entirely rather than commenting it out. If the goal is to use the default value for unbundle (which is likely false), removing the line makes the configuration cleaner and avoids potential confusion from stale commented-out code.

export default defineConfig({
entry: 'src/**/*.ts',
unbundle: true,
// unbundle: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability, it's preferable to remove this line entirely rather than commenting it out. If the goal is to use the default value for unbundle (which is likely false), removing the line makes the configuration cleaner and avoids potential confusion from stale commented-out code.

'src/index.ts',
],
unbundle: true,
// unbundle: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability, it's preferable to remove this line entirely rather than commenting it out. If the goal is to use the default value for unbundle (which is likely false), removing the line makes the configuration cleaner and avoids potential confusion from stale commented-out code.

@codecov
Copy link

codecov bot commented Oct 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.11%. Comparing base (1208221) to head (809a70f).
⚠️ Report is 1 commits behind head on next.

Additional details and impacted files
@@           Coverage Diff           @@
##             next     #350   +/-   ##
=======================================
  Coverage   86.11%   86.11%           
=======================================
  Files         279      279           
  Lines        7995     7995           
  Branches     1204     1190   -14     
=======================================
  Hits         6885     6885           
  Misses       1110     1110           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@fengmk2 fengmk2 merged commit 75376c7 into next Oct 4, 2025
13 checks passed
@fengmk2 fengmk2 deleted the disable-unbundle branch October 4, 2025 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments