fix(nextjs): use out/ as default output dir when output is export

[asumaran]

Current Behavior

The getOutputs() function in the @nx/next plugin only reads distDir from the resolved Next.js config to determine the build output directory. When a project uses output: 'export' (for static site generation), Next.js generates output in out/ by default, but the plugin ignores this and always defaults to .next/.

This causes Nx to cache/restore .next/ instead of out/, which breaks deployment pipelines that depend on the out/ directory for static export builds.

Edge cases

Config	Expected output dir	Before this PR	After this PR
{} (default)	.next	.next	.next
{ distDir: 'build' }	build	build	build
{ output: 'export' }	out	.next	out
{ output: 'export', distDir: 'custom' }	custom	custom	custom
{ output: 'standalone' }	.next	.next	.next

Expected Behavior

When output: 'export' is set in the Next.js config, the plugin should use out/ as the default output directory (matching Next.js behavior), unless an explicit distDir is also specified (in which case distDir takes precedence).

The priority is:

1. Explicit distDir -> use distDir
2. output === 'export' without distDir -> use 'out'
3. Default -> use '.next'

Changes

• Modified getOutputs() in packages/next/src/plugins/plugin.ts to extract a unified resolvedConfig and check for output: 'export'
• Added 3 test cases in packages/next/src/plugins/plugin.spec.ts:
  • output: 'export' with integrated project -> outputs point to out/
  • output: 'export' with root project -> outputs point to out/
  • output: 'export' + custom distDir -> distDir takes precedence

Related Issue(s)

N/A - discovered via broken deployment pipeline when using output: 'export' in Next.js projects within an Nx monorepo.

[netlify]

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	70aff58

[netlify]

👷 Deploy request for nx-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	70aff58