-
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): support workspace libs with standalone Next.js app #16471
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -152,14 +152,14 @@ describe('next library', () => { | |||
expect(appTree.read('my-lib/src/index.ts', 'utf-8')).toContain( | |||
'React client components' | |||
); | |||
expect(appTree.read('my-lib/src/server.ts', 'utf-8')).toContain( | |||
expect(appTree.read('my-lib/src/server.tsx', 'utf-8')).toContain( |
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.
Had to generate with a default component, otherwise the Standalone app complains about no exports being found from module.
4c7093c
to
0130b11
Compare
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 fixes the setup when generating and using workspace libs in a Next.js standalone app.
@nx/next:lib
is used, babel files should not be generated since we are using SWC.compilerOptions.paths: {}
should not exist for standalonetsconfig.json
, because migrating after generating lib will override the base paths intsconfig.base.json
file.