… nextjs official adapter (#187) Fixes #165, #142, #127, #121, #115 This PR will be released as 0.5.0-beta.1. It will remain beta until next.config.js' [experimental.adapterPath](https://nextjs.org/docs/app/api-reference/config/next-config-js/adapterPath) is no longer experimental. This PR requires at least Next.js [v16.1.1-canary.19](https://github.com/vercel/next.js/releases/tag/v16.1.1-canary.19) as it relies on [Image Custom Cache Handler](https://nextjs.org/docs/app/api-reference/config/next-config-js/incrementalCacheHandlerPath#image-optimization-caching). While it's not ideal to depend upon experimental or canary features, this aligns with cdk-nextjs' design philosophy of not tampering with Next.js internals and relying on public APIs wherever possible. - [X] Use S3 + DynamoDB as Next.js Cache replacing EFS - [X] Create `NextjsCache` - [X] Remove `NextjsAssetDeployment` - [x] Fix APP_PAGE cahe kind with `⨯ Error: failed to pipe response` error by storing as utf8 instead of base64 - [X] .next/cdk-nextjs-init-cache - fill with fetch and prerender json values - [X] Run `next build` on host machine, not in container - simplifying build process and reducing build time. - [x] `buildContext` is replaced with `buildDirectory` - [x] Replace sharp with linux musl libvips since host machine is likely diff arch and platform then cloud/runtime - [X] Use Next.js Official [Adapters](https://nextjs.org/docs/app/api-reference/config/next-config-js/adapterPath) to simplify next.config.ts management. - [X] `NextjsRegionalFunctions` now supports streaming (since API GW now supports it) - [X] Improve docs by writing caching, pruning, and nextjs build output guide - [X] Upgrade examples to Next.js 16 - [X] Upgrade Node.js to 24 (LTS) - [x] Ensure e2e tests passing - [X] Explore usage of S3 Directory Buckets (One Zone Express) for lower cost and faster response times for cache bucket. Decided not to use it. See #191 ## Follow up Work - Had to unfortunately include `public/` in image, #193 will fix this and allow us to dynamically pull public images from s3. - Fix flaky/failing isr and revalidation e2e tests in #194 --------- Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Uh oh!

Fix flaky/failing isr and revalidation e2e tests #194

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions