feat: rolldownConfig#3887
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughConsolidates Rollup and Rolldown handling into a unified bundler abstraction: introduces Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
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. Comment |
commit: |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@src/build/vite/bundler.ts`:
- Around line 77-99: The current Rollup config creation in rollupConfig uses
defu with plugins: [inject(base.env.inject), alias({ entries: base.aliases })],
which overrides and drops any plugins present in commonConfig because defu does
not merge arrays; update the plugins value to explicitly concatenate
commonConfig.plugins (or an empty array) with the new plugins so base build
plugins (virtuals/replace/externals, etc.) are preserved — locate rollupConfig
and change the plugins assignment to merge commonConfig.plugins with
inject(base.env.inject) and alias({ entries: base.aliases }) (keep existing use
of defu, NODE_MODULES_RE, libChunkName, and other output settings intact).
In `@src/build/vite/plugin.ts`:
- Around line 184-186: The thrown Error message still says "Nitro rollup config"
while the code uses bundler terminology; update the message in the block that
checks ctx.bundlerConfig (the throw new Error(...) statement) to use consistent
phrasing such as "Nitro bundler config is not initialized yet." so it references
bundlerConfig instead of rollup config.
No description provided.