-
Notifications
You must be signed in to change notification settings - Fork 26.1k
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
docs: mention missing optimized by default packages in optimizePackageImports
#60058
Conversation
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
docs/02-app/02-api-reference/05-next-config-js/optimizePackageImports.mdx
Outdated
Show resolved
Hide resolved
docs/02-app/02-api-reference/05-next-config-js/optimizePackageImports.mdx
Show resolved
Hide resolved
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.
I can see this going either way – there are advantages for linking back to the source code directly. Regardless, given there's some list here now, it makes sense to keep the list as close as possible.
I thought about linking to the code directly but ran into an issue. If we link to the current code, it will be outdated after a while because it won't be updated, and if we link to the Canary branch, the line numbers will change after editing the file in later commits. |
Source:
next.js/packages/next/src/server/config.ts
Lines 827 to 886 in 9986e82