opennextjs-aws

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

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

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

Changes:

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

Changes:

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

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

Add support for pnpm package manager

Changes:

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

Node.js 18 global fetch API instead of node-fetch polyfill

Changes:

• Replaced node-fetch polyfill with Node.js 18 global fetch API #19 — @fwang
• Display OpenNext version in console output #19 — @fwang

Middleware function will not be created if middleware is not used in your Next.js app.

Changes:

• Do not create middleware function if middleware is not used in the Next.js app #14 — @fwang
• Change entire code base to TypeScript #14 — @fwang

Add support for image optimization.

Changes:

• Add support for image optimization #12 — @fwang

Add support for middleware.

Changes:

• Add support for middleware #10 — @fwang

First release with basic features working, including SSG, SSR, dynamic routes, and API routes.

Changes:

• Configure standalone mode using environment variable #1 — @khuezy