v3.0.3

Changes

• 71b3347: fix: look for required-server-files.json in outputPath. Thanks @MaksymKupko
• 1524dd3: Perf: Add some new cache and queue options. Also fix an error being logged for S3 NoSuchKey
• bc26e9a: Fix for readonly headers lambda@edge
• 6032493: Fix for lambda streaming on empty body
• 22e80d7: Fix env file not being copied in V3
• a46d3fc: Fix 404 when no route match at all
• 3ff4909: Fix incorrect filter logic when copying traced files Thanks @vladiulianbogdan

New Cache and queue options

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;

Fix for lambda streaming with empty body

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"