-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pref: remove regexp external in node_polyfill #998
Conversation
WalkthroughThis update focuses on enhancing the performance and simplification of the Mako build tool. It includes the removal of unnecessary debug print statements in the module concatenation process and streamlines the handling of node polyfills by removing complex external configurations in favor of more straightforward settings. These changes aim to improve the build process's efficiency and maintainability. Changes
Assessment against linked issues
Poem
TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (2)
- crates/mako/src/plugins/farm_tree_shake/shake/module_concatenate.rs (2 hunks)
- crates/mako/src/plugins/node_polyfill.rs (2 hunks)
Files skipped from review due to trivial changes (1)
- crates/mako/src/plugins/farm_tree_shake/shake/module_concatenate.rs
Additional comments: 1
crates/mako/src/plugins/node_polyfill.rs (1)
- 27-32: The simplification of external configurations for empty modules using
ExternalConfig::Basic
with an empty string is a clear and concise approach. However, it's important to verify that this change does not introduce any unintended side effects, especially in scenarios where these modules or their/promise
counterparts might be expected to resolve to non-empty values.
Close #997
跑 just bench 性能上没明显区别,但应该不需要用到正则。
Summary by CodeRabbit