Open-source Next.js adapter for AWS
MIT License
Bot releases are visible (Hide)
Published by github-actions[bot] 27 days ago
Published by github-actions[bot] about 1 month ago
Published by github-actions[bot] about 2 months ago
Published by github-actions[bot] about 2 months ago
InternalResult
body is now a ReadableStream
instead of a stringenableCacheInterception
will need to have the correct permission (and environment variable) to access the incremental and tag cache as well as the queue (By default S3, DynamoDb, SQS )Published by github-actions[bot] 3 months ago
Published by github-actions[bot] 3 months ago
resolve
ESBuild plugin. Thanks @costinsinreplacement
ESBuild plugin. Thanks @costinsinfile://
protocol when importing config on Windows. Thanks @costinsinPublished by github-actions[bot] 4 months ago
Published by github-actions[bot] 4 months ago
NoSuchKey
and AccessDenied
error logs are now only in debug ( These are expected errors )dynamodb-lite
, s3-lite
and sqs-lite
that were using the next patched version of fetchFor more info see #444
Published by github-actions[bot] 4 months ago
This releases introduces some new cache and queue options that uses aws4fetch instead of the aws sdk. This can results in up to 300ms less cold start. Here is how to use it in your open-next.config.ts
file :
import type { OpenNextConfig } from 'open-next/types/open-next'
const config = {
default: {
override: {
tagCache: 'dynamodb-lite',
incrementalCache: 's3-lite',
queue: 'sqs-lite'
},
},
} satisfies OpenNextConfig
export default config;
On some aws accounts the response can hang if the body is empty. This releases includes an env variable that will force write to the stream if the stream is empty. Only uses this if you have this issue with your account and region
To enable this you should set the OPEN_NEXT_FORCE_NON_EMPTY_RESPONSE
environment variable to "true"
Published by github-actions[bot] 5 months ago
Published by github-actions[bot] 5 months ago
Published by github-actions[bot] 6 months ago
This is the V3 of OpenNext. It includes some breaking changes and cannot be used as a drop-in replacement for V2. If your IAC is using OpenNext V2, you will need to update it to use V3.
If you are using OpenNext V2, please refer to the migration guide to upgrade to V3.
Published by github-actions[bot] 7 months ago
Published by github-actions[bot] 7 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 9 months ago
Published by github-actions[bot] 10 months ago
Published by github-actions[bot] 11 months ago