v0.9.0

404 Page Support

The server function now has the capability to serve out 404 pages in both regional and edge mode.

In this release, we have implemented significant improvements in the way the server function handles requests for 404 pages and requests for files in your /public folder. These requests had to be handled differently depending on whether the server function is deployed as regional or edge. Read more about it here.

Changes

• 787c1b2: Support Next.js 404 pages
• 6395849: Fix "Cannot find package 'next'"

v0.8.2

Changes

• e5b5204: Handle next build error

v0.8.1

Patch Changes

• bdd29d1: Fix spawn error on Windows

v0.8.0

Running at edge

The server function can now be deployed to Lambda@Edge and run at the edge. Read more about running at edge.

In this release, OpenNext also moved away from using the undocumented minimalMode when building your Next.js app. OpenNext now uses the standard next build command. Read more about this change.

Changes:

• 5a4455e: Remove minimal mode
• 5a4455e: Add support for running server with Lambda@Edge
• 5a4455e: Server: handle undefined response status code
• 5a4455e: Turn on inline sourcemap when OPEN_NEXT_DEBUG is set

v0.7.0

OpenNext now supports NextAuth.js.

Starting from version 0.7.0, the server, middleware, and image optimization function code are now minified, which will reduce Lambda cold start times. You can see how to build in debug mode and disable minification.

Changes:

• fix: Fix next-auth middleware not working on Lambda #38 — @khuezy
• Add debug mode #46 — @fwang

v0.6.0

OpenNext now uses arm64 architecture for image optimization.

Starting v0.6.0, the sharp library is compiled against the arm64 architecture and is intended to run on AWS Lamba Arm/Graviton2 architecture. Learn about the better cost-performance offered by AWS Graviton2 processors.

Changes:

• Create image optimization function in arm64 architecture #37 — @fwang
• fix: delete request body from server adapter #30 — @khuezy
• docs(readme): fix typo in quick start section #34 — @MattFerreira18

v0.5.2

Changes:

• Add support for Next.js "src" directory #26 — @fwang

v0.5.1

Changes:

• Add support for .cjs and .mjs next config #25 — @fwang

v0.5.0

OpenNext now supports monorepos managed with npm, yarn, and pnpm!

If you are interested in how it works behind the scenes:

• How monorepos are bundled; and
• Work around for getting process.cwd() to work in your app

Changes:

• Fix server-function bundle structure when Next.js is inside a monorepo #21 — @fwang
• Add full monorepo support for npm, yarn, and pnpm #23 — @fwang

v0.4.2

Add support for pnpm package manager

Changes:

• Add support for pnpm package manager #20 — @fwang