search

sladg / nextjs-lambda

Lambda deployments for Nextjs12 & Nextjs13 (standalone). Easy CLI commands to get your standalone Next output to run in AWS Lambda (not @Edge)! Uses CDK in behind and produces code zips importable to Terraform, Serverless, Azure, etc.
MIT License
169 stars 19 forks source link

specify next 13 in docs #53

Closed sennett closed 1 year ago

sennett commented 1 year ago

I found that Next 12 didn't work for me - there was no directory .next/standalone in built output. This PR highlights Next 13 requirement.

Related: https://github.com/sladg/nextjs-lambda/issues/51

dtesta commented 1 year ago

@sennett depending on your version of Next 12, the flag may have still been experimental:

module.exports = {
    experimental: {
        outputStandalone: true,
    }
}

https://nextjs.org/blog/next-12-1#self-hosted-nextjs-improvements

Edit: I think it was only experimental in 12.1, then moved to stable for 12.2 on

sladg commented 1 year ago

I think it would make sense to specify Next version as a peer dependency? ^12.2 || ^13 seems to be what we are aiming for

sladg commented 1 year ago

Closing, peer definition will be resolved as part of #40