-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
fix(nextjs): inline dev-only dependencies and add e2e test to catch issues #16890
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -177,6 +177,12 @@ describe('Next.js Applications', () => { | |||
`dist/packages/${appName}/public/shared/ui/hello.txt` | |||
); | |||
|
|||
// Check that compiled next config does not contain bad imports | |||
const nextConfigPath = `dist/packages/${appName}/next.config.js`; |
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 thought we were adding a lint
rule. Is this just a stand-in until we have that set up?
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'll add the lint rule, but also want to make sure it doesn't get into the built file in case we missed something in lint.
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
This PR moves the dev-only imports to the dev/build phase only. This prevents the imports from being added to the compiled
next.config.js
file.Current Behavior
Expected Behavior
Related Issue(s)
Fixes #16882