@netlify/plugin-nextjs 5.0.0-rc.7 → 5.0.0

package/README.md

@@ -1,105 +1,18 @@
-# Next.js Runtime
-
-Next.js is supported natively on Netlify, and in most cases you will not need to install or
-configure anything. This repo includes the packages used to support Next.js on Netlify.
-
-## Lambda Folder structure:
-
-For a simple next.js app
-
-```
-/___netlify-server-handler
-├── .netlify
-│   ├── tags-manifest.json
-│   └── dist // the compiled runtime code
-│       └── run
-│           ├── handlers
-│           │   ├── server.js
-│           │   └── cache.cjs
-│           └── next.cjs
-├── .next // or distDir name from the next.config.js
-│   └── // content from standalone
-├── run-config.json // the config object from the required-server-files.json
-├── node_modules
-├── ___netlify-server-handler.json
-├── ___netlify-server-handler.mjs
-└── package.json
-```
-
-## Testing
-
-The repo includes two types of tests: e2e tests in the repo that use Playwright, integration tests
-that use Vitest.
-
-By default the e2e and integration tests run against the latest version of Next.js. To run tests
-against a specific version, set the `NEXT_VERSION` environment variable to the desired version.
-
-By default, PRs will run the integration tests against the latest version of Next.js. To run tests
-against `latest`, `canary` and `13.5.1`, apply the `test all versions` label to the PR when you
-create it. These also run nightly and on release PRs.
-
-### Integration testing
-
-> **Prerequisite** Run `npm run build` before running integration tests.
-
-How to add new integration test scenarios to the application:
-
-1. Create a new folder under `tests/fixtures/<your-name>`
-2. Adapt the `next.config.js` to be a standalone application
-3. Create a `postinstall` script that runs the `next build`. It's important to notice that the
-   integration tests rely on a already built next.js application in this folder. They rely on the
-   `.next` folder.
-4. Add your test
-
-> Currently the tests require a built version of the `dist/run/handlers/cache.cjs` so you need to
-> run `npm run build` before executing the integration tests.
-
-In addition, the integration tests need to be prepared before first use. You can do this by running
-`npm run pretest`. To speed up this process and build only the fixtures whose name starts with a
-given prefix, run `npm run pretest -- <prefix>`.
-
-### E2E testing
-
-> **Prerequisite**
->
-> Needs the `netlify-cli` installed and being logged in having access to Netlify Testing
-> Organization
-
-The e2e tests can be invoked with `npm run e2e` and perform a full e2e test. This means they do the
-following:
-
-1. Building the next-runtime (just running `npm run build` in the repository)
-2. Creating a temp directory and copying the provided fixture over to the directory.
-3. Packing the runtime with `npm pack` to the temp directory.
-4. Installing the runtime from the created zip artifact of `npm pack` (this is like installing a
-   node_module from the registry)
-5. Creating a `netlify.toml` inside the temp directory of the fixture and adding the runtime as a
-   plugin.
-6. Running `netlify deploy --build` invoking the runtime. This will use the
-   [next-runtime-testing](https://app.netlify.com/sites/next-runtime-testing/overview) as site to
-   deploy to.
-7. Using the `deployId` and `url` of the deployed site to run some
-   [playwright](https://playwright.dev/) tests against, asserting the correctness of the runtime.
-8. After the tests where run successfully, it will delete the deployment again and clean everything
-   up. In case of a failure, the deploy won't be cleaned up to leave it for troubleshooting
-   purposes.
-
-> [!TIP] If you'd like to always keep the deployment and the local fixture around for
-> troubleshooting, run `E2E_PERSIST=1 npm run e2e`.
-
-### Next.js tests
-
-There is a script `run-local-test.sh` and GitHub workflow that runs the e2e tests from the Next.js
-repo against this repo. It requires that `next.js` is checked out in the same parent directory as
-this repo, and is run from this repo with `./run-local-test.sh your-test-pattern-here`.
-
-#### cleanup old deploys
-
-To cleanup old and dangling deploys from failed builds you can run the following script:
-
-```bash
-npx tsx ./tools/e2e/cleanup-deploys.ts
-```
-
-This will cleanup all created deploys on the
-[next-runtime-testing](https://app.netlify.com/sites/next-runtime-testing/overview) site.
+![Next.js Runtime](https://github.com/netlify/next-runtime/raw/main/next-js-runtime.png)
+
+# `@netlify/plugin-nextjs`
+
+<p align="center">
+  <a aria-label="npm version" href="https://www.npmjs.com/package/@netlify/plugin-nextjs">
+    <img alt="" src="https://img.shields.io/npm/v/@netlify/plugin-nextjs">
+  </a>
+  <a aria-label="MIT License" href="https://img.shields.io/npm/l/@netlify/plugin-nextjs">
+    <img alt="" src="https://img.shields.io/npm/l/@netlify/plugin-nextjs">
+  </a>
+</p>
+
+This package handles the build process and creates the runtime environment for Next.js sites on
+Netlify. You should not normally need to install it yourself, as it is used automatically during
+builds of Next.js sites. See
+[the docs for using Next.js on Netlify](https://docs.netlify.com/frameworks/next-js/overview/) for
+more details.

package/dist/build/image-cdn.js

@@ -6,7 +6,7 @@
     
 import {
   setImageConfig
-} from "../esm-chunks/chunk-FMO6SJ5E.js";
+} from "../esm-chunks/chunk-MCEOSJH6.js";
 import "../esm-chunks/chunk-5JVNISGM.js";
 export {
   setImageConfig

package/dist/esm-chunks/{chunk-FMO6SJ5E.js → chunk-MCEOSJH6.js}

@@ -1565,15 +1565,27 @@ var setImageConfig = async (ctx) => {
   if (imageLoader !== "default") {
     return;
   }
-  ctx.netlifyConfig.redirects.push({
-    from: imageEndpointPath,
-    // w and q are too short to be used as params with id-length rule
-    // but we are forced to do so because of the next/image loader decides on their names
-    // eslint-disable-next-line id-length
-    query: { url: ":url", w: ":width", q: ":quality" },
-    to: "/.netlify/images?url=:url&w=:width&q=:quality",
-    status: 200
-  });
+  ctx.netlifyConfig.redirects.push(
+    {
+      from: imageEndpointPath,
+      // w and q are too short to be used as params with id-length rule
+      // but we are forced to do so because of the next/image loader decides on their names
+      // eslint-disable-next-line id-length
+      query: { url: ":url", w: ":width", q: ":quality" },
+      to: "/.netlify/images?url=:url&w=:width&q=:quality",
+      status: 200
+    },
+    // when migrating from @netlify/plugin-nextjs@4 image redirect to ipx might be cached in the browser
+    {
+      from: "/_ipx/*",
+      // w and q are too short to be used as params with id-length rule
+      // but we are forced to do so because of the next/image loader decides on their names
+      // eslint-disable-next-line id-length
+      query: { url: ":url", w: ":width", q: ":quality" },
+      to: "/.netlify/images?url=:url&w=:width&q=:quality",
+      status: 200
+    }
+  );
   if (remotePatterns?.length !== 0 || domains?.length !== 0) {
     ctx.netlifyConfig.images ||= { remote_images: [] };
     ctx.netlifyConfig.images.remote_images ||= [];

package/dist/esm-chunks/{package-NR7AMHPP.js → package-F3THTZDD.js}

@@ -8,7 +8,7 @@ import "./chunk-5JVNISGM.js";
 
 // package.json
 var name = "@netlify/plugin-nextjs";
-var version = "5.0.0-rc.7";
+var version = "5.0.0";
 var description = "Run Next.js seamlessly on Netlify";
 var main = "./dist/index.js";
 var type = "module";
@@ -53,7 +53,7 @@ var homepage = "https://github.com/netlify/next-runtime-minimal#readme";
 var devDependencies = {
   "@fastly/http-compute-js": "1.1.4",
   "@netlify/blobs": "^7.0.1",
-  "@netlify/build": "^29.36.4",
+  "@netlify/build": "^29.37.2",
   "@netlify/edge-bundler": "^11.3.0",
   "@netlify/edge-functions": "^2.3.1",
   "@netlify/eslint-config-node": "^7.0.1",

package/dist/index.js

@@ -35,7 +35,7 @@ import {
 } from "./esm-chunks/chunk-72ZI2IVI.js";
 import {
   setImageConfig
-} from "./esm-chunks/chunk-FMO6SJ5E.js";
+} from "./esm-chunks/chunk-MCEOSJH6.js";
 import {
   PluginContext
 } from "./esm-chunks/chunk-3NYX5FXN.js";

package/dist/run/handlers/cache.cjs

@@ -925,12 +925,17 @@ var NetlifyCacheHandler = class {
       const lastModified = Date.now();
       span.setAttributes({ key, lastModified, blobKey });
       console.debug(`[NetlifyCacheHandler.set]: ${key}`);
+      let value = data;
       if (data?.kind === "ROUTE") {
-        data.body = data.body.toString("base64");
+        value = {
+          ...data,
+          // @ts-expect-error gotta find a better solution for this
+          body: data.body.toString("base64")
+        };
       }
       await this.blobStore.setJSON(blobKey, {
         lastModified,
-        value: data
+        value
       });
       if (data?.kind === "PAGE") {
         const requestContext = (0, import_request_context.getRequestContext)();

package/dist/run/handlers/tracing.js

@@ -51202,7 +51202,7 @@ var import_sdk_trace_node = __toESM(require_src14(), 1);
 var import_semantic_conventions = __toESM(require_src(), 1);
 var {
   default: { version, name }
-} = await import("../../esm-chunks/package-NR7AMHPP.js");
+} = await import("../../esm-chunks/package-F3THTZDD.js");
 var sdk = new import_sdk_node.NodeSDK({
   resource: new import_resources.Resource({
     [import_semantic_conventions.SEMRESATTRS_SERVICE_NAME]: name,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@netlify/plugin-nextjs",
-  "version": "5.0.0-rc.7",
+  "version": "5.0.0",
   "description": "Run Next.js seamlessly on Netlify",
   "main": "./dist/index.js",
   "type": "module",