@nx/next 23.0.0 → 23.1.0-beta.1

package/README.md

@@ -7,13 +7,12 @@
 
 <div style="text-align: center;">
 
-[![CircleCI](https://circleci.com/gh/nrwl/nx.svg?style=svg)](https://circleci.com/gh/nrwl/nx)
 [![License](https://img.shields.io/npm/l/@nx/workspace.svg?style=flat-square)]()
 [![NPM Version](https://badge.fury.io/js/nx.svg)](https://www.npmjs.com/package/nx)
 [![Semantic Release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg?style=flat-square)]()
 [![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/)
-[![Join the chat at https://gitter.im/nrwl-nx/community](https://badges.gitter.im/nrwl-nx/community.svg)](https://gitter.im/nrwl-nx/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 [![Join us on the Official Nx Discord Server](https://img.shields.io/discord/1143497901675401286?label=discord)](https://go.nx.dev/community)
+[![Nx Sandboxing](https://staging.nx.app/workspaces/62d013ea0852fe0a2df74438/sandbox-badge.svg)](https://nx.dev/docs/features/ci-features/sandboxing)
 
 </div>
 

package/dist/src/generators/application/files/common/index.d.ts__tmpl__

@@ -1,3 +1,4 @@
+/// <reference types="@nx/next/typings/style.d.ts" />
 /* eslint-disable @typescript-eslint/no-explicit-any */
 declare module '*.svg' {
   const content: any;

package/dist/src/generators/application/files/common/tsconfig.json__tmpl__

@@ -29,6 +29,7 @@
       "<%= layoutTypeSrcPath %>",
       "<%= layoutTypeDistPath %>",
     <% } %>
+    "index.d.ts",
     "next-env.d.ts"
   ],
   "exclude": ["node_modules", "jest.config.ts", "jest.config.cts", "<%= rootPath %>**/*.spec.ts", "<%= rootPath %>**/*.test.ts"]

package/dist/src/migrations/update-23-1-0/ai-instructions-for-next-15.md

@@ -0,0 +1,57 @@
+# Next.js 14 -> 15 Migration Instructions for LLM
+
+Migrate the Nx workspace's Next.js projects from 14 to 15. Run the codemod first, fix the rest by hand, build after each project.
+
+## Step 1: Codemod
+
+```bash
+npx @next/codemod@canary upgrade 15
+```
+
+Pin to `15` (not `latest` - that now resolves to 16). The `@canary` tag is what Next ships the upgrade codemod on. Handles most async-API rewrites. Review the diff.
+
+## Step 2: React 19 (App Router only)
+
+Next 15 App Router requires React 19. Page Router can stay on React 18. For App Router projects, also run the React 18 -> 19 migration.
+
+## Step 3: Async request APIs (main breaking change)
+
+`cookies`, `headers`, `draftMode`, `params`, `searchParams` are now async. Codemod covers most; fix leftovers.
+
+```tsx
+// before
+const { slug } = params;
+// after
+const { slug } = await props.params;
+```
+
+Make the component / handler `async` and `await` the value.
+
+App Router only - Pages Router `getServerSideProps` / `getStaticProps` / `getStaticPaths` `context.params` is NOT async; leave it unchanged.
+
+## Step 4: Caching defaults changed
+
+No longer cached by default: `fetch`, GET route handlers, client navigations. Re-add caching where you relied on it.
+
+- `fetch(url, { cache: 'force-cache' })`
+- Route handler: `export const dynamic = 'force-static'`
+
+## Step 5: Misc
+
+- `@next/font` removed -> import from `next/font`.
+- Route `runtime: 'experimental-edge'` -> `runtime: 'edge'`.
+- `next.config` renames: `experimental.bundlePagesExternals` -> top-level `bundlePagesRouterDependencies`; `experimental.serverComponentsExternalPackages` -> top-level `serverExternalPackages`.
+- `NextRequest.geo` / `request.ip` removed (e.g. in middleware) -> read from headers (`x-forwarded-for`, platform geo headers).
+
+## Validate
+
+```bash
+nx run PROJECT:build
+nx affected -t build,lint,test
+```
+
+## Notes for LLM
+
+- Codemod first, then manual.
+- One project at a time, build after each.
+- Skip Step 2 for Page Router projects.

package/dist/src/migrations/update-23-1-0/upgrade-to-next-15.md

@@ -0,0 +1,33 @@
+#### Upgrade Next.js 14 to 15
+
+Bumps Next.js from 14 to 15 (and `eslint-config-next` to match). The main breaking change is that the request APIs (`params`, `searchParams`, `cookies`, `headers`, `draftMode`) are now asynchronous. App Router projects also require React 19; Page Router projects can stay on React 18. Read more in the [Next.js 15 upgrade guide](https://nextjs.org/docs/app/guides/upgrading/version-15).
+
+The paired AI instructions migration walks an agent through the full set of changes. The common ones are shown below.
+
+#### Examples
+
+##### Before
+
+```tsx title="app/blog/[slug]/page.tsx"
+export default function Page({ params, searchParams }) {
+  const { slug } = params;
+  const query = searchParams.q;
+  return <h1>{slug}</h1>;
+}
+```
+
+##### After
+
+```tsx title="app/blog/[slug]/page.tsx"
+export default async function Page(props) {
+  const { slug } = await props.params;
+  const { q: query } = await props.searchParams;
+  return <h1>{slug}</h1>;
+}
+```
+
+`cookies`, `headers`, and `draftMode` are awaited the same way (`const store = await cookies();`).
+
+#### Page Router
+
+Pages Router data functions are not affected: `getServerSideProps` / `getStaticProps` / `getStaticPaths` `context.params` stays synchronous - leave it unchanged.

package/dist/src/utils/versions.d.ts

@@ -6,7 +6,7 @@ export declare const next14Version = "~14.2.35";
 export declare const nextVersion = "~16.1.6";
 export declare const eslintConfigNext16Version = "^16.1.6";
 export declare const eslintConfigNext15Version = "^15.5.18";
-export declare const eslintConfigNext14Version = "~14.2.35";
+export declare const eslintConfigNext14Version = "^15.5.18";
 export declare const eslintConfigNextVersion = "^16.1.6";
 export declare const sassVersion = "1.97.2";
 export declare const tsLibVersion = "^2.3.0";

package/dist/src/utils/versions.js

@@ -10,7 +10,8 @@ exports.next14Version = '~14.2.35';
 exports.nextVersion = exports.next16Version;
 exports.eslintConfigNext16Version = '^16.1.6';
 exports.eslintConfigNext15Version = '^15.5.18';
-exports.eslintConfigNext14Version = '~14.2.35';
+// eslint-config-next 14 lacks ESLint v9 support, so Next.js 14 (being removed) uses 15.
+exports.eslintConfigNext14Version = '^15.5.18';
 exports.eslintConfigNextVersion = exports.eslintConfigNext16Version;
 exports.sassVersion = '1.97.2';
 exports.tsLibVersion = '^2.3.0';

package/dist/typings/style.d.ts

@@ -0,0 +1,21 @@
+// TS 6.0 enables `noUncheckedSideEffectImports`, which errors on plain
+// `import './x.css'` unless the module is declared. Equally-specific wildcard
+// patterns resolve by registration order, so this bare '*.css' can shadow
+// next's own typed '*.module.css'; the class-map default export keeps
+// CSS-module property access working even when it shadows.
+declare module '*.css' {
+  const classes: { readonly [key: string]: string };
+  export default classes;
+}
+declare module '*.scss' {
+  const classes: { readonly [key: string]: string };
+  export default classes;
+}
+declare module '*.sass' {
+  const classes: { readonly [key: string]: string };
+  export default classes;
+}
+declare module '*.less' {
+  const classes: { readonly [key: string]: string };
+  export default classes;
+}

package/migrations.json

@@ -20,6 +20,15 @@
       "description": "Rename imports of `createNodesV2` from `@nx/next/plugin` to the canonical `createNodes` export.",
       "implementation": "./dist/src/migrations/update-23-0-0/migrate-create-nodes-v2-to-create-nodes",
       "documentation": "./dist/src/migrations/update-23-0-0/migrate-create-nodes-v2-to-create-nodes.md"
+    },
+    "update-23-1-0-create-ai-instructions-for-next-15": {
+      "version": "23.1.0-beta.0",
+      "requires": {
+        "next": ">=15.0.0 <16.0.0"
+      },
+      "description": "Create AI instructions to help migrate workspaces from Next.js 14 to 15.",
+      "prompt": "./dist/src/migrations/update-23-1-0/ai-instructions-for-next-15.md",
+      "documentation": "./dist/src/migrations/update-23-1-0/upgrade-to-next-15.md"
     }
   },
   "packageJsonUpdates": {
@@ -55,6 +64,22 @@
           "alwaysAddToPackageJson": false
         }
       }
+    },
+    "23.1.0": {
+      "version": "23.1.0-beta.0",
+      "requires": {
+        "next": ">=14.0.0 <15.0.0"
+      },
+      "packages": {
+        "next": {
+          "version": "~15.5.18",
+          "alwaysAddToPackageJson": false
+        },
+        "eslint-config-next": {
+          "version": "^15.5.18",
+          "alwaysAddToPackageJson": false
+        }
+      }
     }
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nx/next",
-  "version": "23.0.0",
+  "version": "23.1.0-beta.1",
   "private": false,
   "description": "The Next.js plugin for Nx contains executors and generators for managing Next.js applications and libraries within an Nx workspace. It provides:\n\n\n- Scaffolding for creating, building, serving, linting, and testing Next.js applications.\n\n- Integration with building, serving, and exporting a Next.js application.\n\n- Integration with React libraries within the workspace. \n\nWhen using Next.js in Nx, you get the out-of-the-box support for TypeScript, Playwright, Cypress, and Jest. No need to configure anything: watch mode, source maps, and typings just work.",
   "repository": {
@@ -78,17 +78,17 @@
     "tslib": "^2.3.0",
     "webpack-merge": "^5.8.0",
     "@phenomnomnominal/tsquery": "~6.2.0",
-    "@nx/devkit": "23.0.0",
-    "@nx/js": "23.0.0",
-    "@nx/eslint": "23.0.0",
-    "@nx/react": "23.0.0",
-    "@nx/web": "23.0.0",
-    "@nx/webpack": "23.0.0"
+    "@nx/devkit": "23.1.0-beta.1",
+    "@nx/js": "23.1.0-beta.1",
+    "@nx/eslint": "23.1.0-beta.1",
+    "@nx/react": "23.1.0-beta.1",
+    "@nx/web": "23.1.0-beta.1",
+    "@nx/webpack": "23.1.0-beta.1"
   },
   "devDependencies": {
-    "@nx/cypress": "23.0.0",
-    "@nx/playwright": "23.0.0",
-    "nx": "23.0.0"
+    "@nx/cypress": "23.1.0-beta.1",
+    "@nx/playwright": "23.1.0-beta.1",
+    "nx": "23.1.0-beta.1"
   },
   "publishConfig": {
     "access": "public"

package/typings/style.d.ts

@@ -0,0 +1,21 @@
+// TS 6.0 enables `noUncheckedSideEffectImports`, which errors on plain
+// `import './x.css'` unless the module is declared. Equally-specific wildcard
+// patterns resolve by registration order, so this bare '*.css' can shadow
+// next's own typed '*.module.css'; the class-map default export keeps
+// CSS-module property access working even when it shadows.
+declare module '*.css' {
+  const classes: { readonly [key: string]: string };
+  export default classes;
+}
+declare module '*.scss' {
+  const classes: { readonly [key: string]: string };
+  export default classes;
+}
+declare module '*.sass' {
+  const classes: { readonly [key: string]: string };
+  export default classes;
+}
+declare module '*.less' {
+  const classes: { readonly [key: string]: string };
+  export default classes;
+}