Uh oh!
There was an error while loading. Please reload this page.
[workbench] disable lazyDiscovery in Next.js workbench apps - #1804
[workbench] disable lazyDiscovery in Next.js workbench apps#1804TooTallNate wants to merge 2 commits into
Conversation
Removes the lazyDiscovery: true option from the nextjs-turbopack and nextjs-webpack workbench next.config.ts files so e2e tests exercise the eager discovery path on the stable branch.
|
🧪 E2E Test ResultsNo test result files found. ❌ Some E2E test jobs failed:
Check the workflow run for details. |
There was a problem hiding this comment.
Pull request overview
Disables Next.js “lazy discovery” in the workbench Next.js apps so CI/e2e on stable exercises the eager discovery path in workflow/next by default.
Changes:
- Remove
workflows: { lazyDiscovery: true }from the webpack and turbopack workbenchnext.config.tsfiles. - Standardize both configs to
export default withWorkflow(nextConfig).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| workbench/nextjs-webpack/next.config.ts | Stops enabling lazyDiscovery via withWorkflow options so the eager builder path is used. |
| workbench/nextjs-turbopack/next.config.ts | Same: removes lazyDiscovery option to ensure eager discovery is exercised in turbopack workbench app. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
lazyDiscovery: truefromworkbench/nextjs-turbopack/next.config.tsandworkbench/nextjs-webpack/next.config.tsstablebranch exercise the eager discovery pathNo published packages change, so no changeset needed.