-
-
Notifications
You must be signed in to change notification settings - Fork 757
feat!: disable requireAsExpression by default #12786
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
Conversation
✅ Deploy Preview for rspack-v2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Rsdoctor Bundle Diff AnalysisFound 5 projects in monorepo, 5 projects with changes. 📊 Quick Summary
📋 Detailed Reports (Click to expand)📁 react-10kPath:
📁 react-1kPath:
📁 react-5kPath:
📁 romePath:
📁 ui-componentsPath:
Generated by Rsdoctor GitHub Action |
📦 Binary Size-limit
🎉 Size decreased by 322.13KB from 47.99MB to 47.68MB (⬇️0.66%) |
d9c4bae to
1708902
Compare
Change the default value of `requireAsExpression` from `true` to `false`. This reduces unnecessary warnings when using `require` as an expression in most common use cases.
1708902 to
ca46bc5
Compare
CodSpeed Performance ReportMerging this PR will degrade performance by 10.75%Comparing Summary
Performance Changes
Footnotes
|
Summary
Change the default value of
requireAsExpressionfromtruetofalse. This reduces unnecessary warnings when usingrequireas an expression in most common use cases.When
requireAsExpressionis enabled, rspack emits a "Critical dependency" warning wheneverrequireis used as an expression (e.g.,var r = require;). By disabling it by default, we avoid these warnings in typical scenarios while still allowing users to opt-in if they need this behavior.Checklist