tech9-cdk-nextjs-standalone
v0.0.9
Published
Deploy a NextJS app to AWS using CDK. Uses standalone build and output tracing.
Downloads
3
Maintainers
Readme
Deploy NextJS with CDK
What is this?
A CDK construct to deploy a NextJS app using AWS CDK. Supported NextJs versions: >=12.3.0+ (includes 13.0.0+)
Uses the standalone output build mode.
Quickstart
Add the dependency [email protected]
to your project along with cdk-nextjs-standalone
.
npm install -D [email protected] cdk-nextjs-standalone
import path from 'path';
import { Nextjs } from 'cdk-nextjs-standalone';
new Nextjs(this, 'Web', {
nextjsPath: './web', // relative path to nextjs project root
});
Documentation
Available on Construct Hub.
Discord Chat
We're in the #open-next channel on the Serverless Stack Discord.
About
Deploys a NextJs static site with server-side rendering and API support. Uses AWS lambda and CloudFront.
There is a new (since Next 12) standalone output mode which uses output tracing to generate a minimal server and static files. This standalone server can be converted into a CloudFront distribution and a lambda handler that handles SSR, API, and routing.
The CloudFront default origin first checks S3 for static files and falls back to an HTTP origin using a lambda function URL.
Benefits
This approach is most compatible with new NextJs features such as ESM configuration, middleware, next-auth, and React server components ("appDir").
The unmaintained @serverless-nextjs project uses the deprecated serverless
NextJs build target which prevents the use of new features.
This construct was created to use the new standalone
output build and newer AWS features like lambda function URLs and fallback origins.
You may want to look at Serverless Stack and its NextjsSite construct for an improved developer experience if you are building serverless applications on CDK.
Dependencies
Built on top of open-next, which was partially built using the original core of cdk-nextjs-standalone.
Heavily based on
- Open-next
- https://github.com/iiroj/iiro.fi/commit/bd43222032d0dbb765e1111825f64dbb5db851d9
- https://github.com/sladg/nextjs-lambda
- https://github.com/serverless-nextjs/serverless-next.js/tree/master/packages/compat-layers/apigw-lambda-compat
- Serverless Stack
- RemixSite construct
- NextjsSite construct
Contribute
Hey there, we value every new contribution a lot 🙏🏼 thank you.
Here is a short HowTo before you get started:
- Please make sure to create a bug first
- Link the bug in your pull request
- Run
yarn build
after you made your changes and before you open a pull request
Breaking changes
v3.0.0: Using open-next for building, ARM64 architecture for image handling, new build options.
v2.0.0: SST wrapper changed, lambda/assets/distribution defaults now are in the
defaults
prop, refactored distribution settings into the new NextjsDistribution construct. If you are upgrading, you must temporarily remove thecustomDomain
on your existing 1.x.x app before upgrading to >=2.x.x because the CloudFront distribution will get recreated due to refactoring, and the custom domain must be globally unique across all CloudFront distributions. Prepare for downtime.