Skip to content
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): read nextConfig path correctly when provided as an option. #20241

Merged
merged 1 commit into from Nov 14, 2023

Conversation

ndcunningham
Copy link
Contributor

closes: #20142

Current Behavior

Expected Behavior

Related Issue(s)

Fixes #

@ndcunningham ndcunningham added the scope: nextjs Issues related to NextJS support for Nx label Nov 14, 2023
@ndcunningham ndcunningham self-assigned this Nov 14, 2023
@ndcunningham ndcunningham requested a review from a team as a code owner November 14, 2023 17:14
Copy link

vercel bot commented Nov 14, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Visit Preview Nov 14, 2023 5:15pm

@ndcunningham ndcunningham merged commit b1bb892 into nrwl:master Nov 14, 2023
7 checks passed
@ndcunningham ndcunningham deleted the fix/next-config-path branch November 14, 2023 18:01
FrozenPandaz pushed a commit that referenced this pull request Nov 17, 2023
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
scope: nextjs Issues related to NextJS support for Nx
Projects
None yet
Development

Successfully merging this pull request may close these issues.

nextConfig function resolves to wrong path in a monorepo
2 participants