[V3] Function splitting

[conico974]

This PR add support for function splitting in open-next It is based on the rewrite server PR, if you want to review start at a50cdf7

Features

• Split next standalone output into multiple bundles.
• Each splitted function could use different wrapper and converter (i.e. 1 on docker, 1 on lambda with streaming, 1 on an ec2 instance or a vps)
• Experimental bundled NextServer. At the moment we use the standalone output, this introduces a lot of unnecessary files into the bundle. With bundled NextServer in my test app, one function could go from 29.9Mb unzipped to 6.3Mb, and that's including almost 1Mb for all the @aws-sdk packages
• Reduced cold start, with the decrease in sizes, it also means that cold start is way better. From 2.5 seconds to around 700ms in a best case scenario (A simple api with few deps)

How to test

You'll need an open-next.config.ts file next to your next.config.js. A simple example of such a file:

import type { BuildOptions } from 'open-next/types/open-next'
const config = {
  default: {
    // debug: true,
    override: {
      wrapper: "aws-lambda-streaming",
    },
  },
  // functions: {},
  functions: {
    ssr: {
      routes: ["app/api/isr/route", "app/api/sse/route", "app/api/revalidateTag/route"],
      patterns: ['api/isr', 'api/sse', 'api/revalidateTag'],
      override: {
        wrapper: "aws-lambda-streaming",
      },
      experimentalBundledNextServer: true
    },
    pageSsr: {
      routes: ["pages/pageSsr"],
      patterns: [ 'pageSsr', "_next/data/BUILD_ID/pageSsr.json"],
      override: {
        wrapper: "node",
        converter: "node",
        generateDockerfile: true,
      },
    },
    edge: {
      // Edge runtime support only app dir routes and page
      runtime: "edge",
     // You could deploy edge runtime both "regional" or "global" (i.e. lambda@edge)
      placement: "regional",
      // Only one route at a time allowed for edge runtime
      routes: ["app/ssr/page"],
      patterns: ["ssr"],
      override: {}
    }

  },
  buildCommand: "echo 'hello world'"
} satisfies BuildOptions

module.exports = config;
export type OpenNextConfig = typeof config

You can now use the corresponding PR in sst to test this https://github.com/sst/sst/pull/3567

TODO

• [x] External middleware/routing (Necessary for internal rewrites to work correctly with splitted function)
• [x] Support edge runtime (On aws you could deploy the edge runtime in lambda@edge or in regular lambda)
• [ ] Add tests
• [x] Make warmer works with splitted function
• [x] Write corresponding PR in sst or in ion

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 51ba372023f97462db65bb7a54947441aba5b9ca

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
open-next	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 6, 2024 9:00am