diff --git a/.github/actions/build-docs/action.yml b/.github/actions/build-docs/action.yml
index 44d6d04..799eff8 100644
--- a/.github/actions/build-docs/action.yml
+++ b/.github/actions/build-docs/action.yml
@@ -2,16 +2,16 @@ name: Build Docs
 description: Build docs pages inside /docs directory
 
 runs:
-    using: 'composite'
-    steps:
-        - name: Install dependencies
-          run: bun install
-          shell: bash
+  using: "composite"
+  steps:
+    - name: Install dependencies
+      run: bun install
+      shell: bash
 
-        - name: Build with Next.js
-          run: bun next build
-          shell: bash
+    - name: Build with Next.js
+      run: bun next build
+      shell: bash
 
-        - name: Export static HTML with Next.js
-          run: bun next export
-          shell: bash
+    - name: Export static HTML with Next.js
+      run: bun next export
+      shell: bash
diff --git a/.github/actions/format/action.yml b/.github/actions/format/action.yml
new file mode 100644
index 0000000..3257b85
--- /dev/null
+++ b/.github/actions/format/action.yml
@@ -0,0 +1,13 @@
+name: Format codebase
+description: Run prettier to check codebase formatting
+
+runs:
+  using: "composite"
+  steps:
+    - name: Install dependencies
+      run: bun install
+      shell: bash
+
+    - name: Run prettier
+      run: bun run prettier:check
+      shell: bash
diff --git a/.github/workflows/check.yml b/.github/workflows/check.yml
index 2a2fc68..ea4c643 100644
--- a/.github/workflows/check.yml
+++ b/.github/workflows/check.yml
@@ -1,15 +1,16 @@
 name: Validate merge requests
 
 on:
-    pull_request:
-        branches:
-            - main
+  pull_request:
+    branches:
+      - main
 
 jobs:
-    validate:
-        runs-on: ubuntu-latest
-        steps:
-            - name: Checkout
-              uses: actions/checkout@v4
-            - uses: oven-sh/setup-bun@v2
-            - uses: ./.github/actions/build-docs
+  validate:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - uses: oven-sh/setup-bun@v2
+      - uses: ./.github/actions/format
+      - uses: ./.github/actions/build-docs
diff --git a/.github/workflows/nextjs.yml b/.github/workflows/nextjs.yml
index f0fe1d8..46ce460 100644
--- a/.github/workflows/nextjs.yml
+++ b/.github/workflows/nextjs.yml
@@ -23,7 +23,7 @@ permissions:
 
 # Allow one concurrent deployment
 concurrency:
-  group: 'pages'
+  group: "pages"
   cancel-in-progress: true
 
 jobs:
diff --git a/.prettierrc b/.prettierrc
new file mode 100644
index 0000000..0adf136
--- /dev/null
+++ b/.prettierrc
@@ -0,0 +1,8 @@
+{
+  "printWidth": 110,
+  "singleQuote": false,
+  "semi": true,
+  "useTabs": false,
+  "tabWidth": 2,
+  "trailingComma": "es5"
+}
diff --git a/bun.lockb b/bun.lockb
index d373d48..126f247 100755
Binary files a/bun.lockb and b/bun.lockb differ
diff --git a/components/Footer.tsx b/components/Footer.tsx
index f7a3cad..c690535 100644
--- a/components/Footer.tsx
+++ b/components/Footer.tsx
@@ -4,9 +4,7 @@ import styles from "../styles/Layout.module.css";
 export default function Footer() {
   return (
     <footer className={styles.footer}>
-      <span>
-        Maintained by the OpenNext community
-      </span>
+      <span>Maintained by the OpenNext community</span>
       <div>
         <a target="_blank" href={SITE.github} rel="noopener noreferrer">
           GitHub
diff --git a/components/Logo.svg.tsx b/components/Logo.svg.tsx
index 5077731..5421e0e 100644
--- a/components/Logo.svg.tsx
+++ b/components/Logo.svg.tsx
@@ -1,12 +1,6 @@
 export default function Logo() {
   return (
-    <svg
-      width="195"
-      height="36"
-      fill="none"
-      viewBox="0 0 195 36"
-      xmlns="http://www.w3.org/2000/svg"
-    >
+    <svg width="195" height="36" fill="none" viewBox="0 0 195 36" xmlns="http://www.w3.org/2000/svg">
       <path
         d="M89.9565 27V2.88H95.8965L108.713 19.908V2.88H113.248V27H108.676L94.4925 8.136V27H89.9565Z"
         fill="currentColor"
@@ -19,10 +13,7 @@ export default function Logo() {
         d="M145.8 27L154.764 14.58L145.944 2.88H151.776L158.4 11.592L164.664 2.88H170.1L161.28 15.12L170.28 27H164.412L157.644 18.072L151.236 27H145.8Z"
         fill="currentColor"
       />
-      <path
-        d="M181.074 27V7.092H172.218V2.88H194.646V7.092H185.79V27H181.074Z"
-        fill="currentColor"
-      />
+      <path d="M181.074 27V7.092H172.218V2.88H194.646V7.092H185.79V27H181.074Z" fill="currentColor" />
       <path
         d="M10.2284 27.3516C8.15422 27.3516 6.40813 26.9473 4.99016 26.1387C3.58391 25.3184 2.5175 24.1641 1.79094 22.6758C1.0761 21.1875 0.718674 19.4473 0.718674 17.4551C0.718674 16.0488 0.841721 14.6719 1.08781 13.3242C1.34563 11.9648 1.72063 10.6699 2.21281 9.43945C2.705 8.20898 3.32024 7.07227 4.05852 6.0293C4.80852 4.98633 5.6757 4.08398 6.66008 3.32227C7.64445 2.54883 8.74602 1.95117 9.96477 1.5293C11.1952 1.10742 12.537 0.896484 13.9902 0.896484C16.9902 0.896484 19.287 1.78125 20.8808 3.55078C22.4863 5.32031 23.289 7.72266 23.289 10.7578C23.289 12.1641 23.1718 13.5527 22.9374 14.9238C22.7148 16.2832 22.3632 17.584 21.8827 18.8262C21.414 20.0566 20.8222 21.1934 20.1073 22.2363C19.3925 23.2676 18.5488 24.1641 17.5761 24.9258C16.6152 25.6875 15.5195 26.2852 14.289 26.7188C13.0702 27.1406 11.7167 27.3516 10.2284 27.3516ZM10.4745 23.748C11.33 23.748 12.1327 23.5957 12.8827 23.291C13.6327 22.9863 14.3183 22.5586 14.9394 22.0078C15.5722 21.4453 16.1347 20.7715 16.6269 19.9863C17.1308 19.2012 17.5527 18.3281 17.8925 17.3672C18.2441 16.4062 18.5136 15.375 18.7011 14.2734C18.8886 13.1602 18.9823 12 18.9823 10.793C18.9823 8.83594 18.5195 7.29492 17.5937 6.16992C16.6796 5.04492 15.373 4.48242 13.6738 4.48242C12.7948 4.48242 11.9687 4.64062 11.1952 4.95703C10.4335 5.26172 9.73039 5.70703 9.08586 6.29297C8.44133 6.86719 7.86711 7.55273 7.3632 8.34961C6.87102 9.13477 6.44914 10.0078 6.09758 10.9688C5.74602 11.9297 5.47649 12.9551 5.28899 14.0449C5.1132 15.123 5.02531 16.248 5.02531 17.4199C5.02531 18.7559 5.23625 19.8984 5.65813 20.8477C6.09172 21.7969 6.71281 22.5176 7.52141 23.0098C8.34172 23.502 9.3261 23.748 10.4745 23.748Z"
         fill="currentColor"
diff --git a/package.json b/package.json
index 5dbab6c..eb81dbe 100644
--- a/package.json
+++ b/package.json
@@ -6,7 +6,10 @@
     "dev": "next dev",
     "build": "next build",
     "start": "next start",
-    "lint": "next lint"
+    "lint": "next lint",
+    "prettier:check": "prettier --check .",
+    "prettier:fix": "prettier --write .",
+    "fix": "bun run prettier:fix"
   },
   "dependencies": {
     "@types/node": "18.11.9",
@@ -18,5 +21,8 @@
     "react": "18.2.0",
     "react-dom": "18.2.0",
     "typescript": "4.9.3"
+  },
+  "devDependencies": {
+    "prettier": "^3.5.2"
   }
 }
diff --git a/pages/_app.mdx b/pages/_app.mdx
index 2e1b362..39b86cd 100644
--- a/pages/_app.mdx
+++ b/pages/_app.mdx
@@ -1,3 +1,3 @@
 export default function App({ Component, pageProps }) {
-  return <Component {...pageProps} />
-}
\ No newline at end of file
+  return <Component {...pageProps} />;
+}
diff --git a/pages/aws/common_issues.mdx b/pages/aws/common_issues.mdx
index 49c66e7..79b3dc5 100644
--- a/pages/aws/common_issues.mdx
+++ b/pages/aws/common_issues.mdx
@@ -63,7 +63,6 @@ This can also happen in app router when a client navigates via NextJS `<Link>` c
 
 The issue might be that your having a folder or file in your `public` directory with an overlapping between the name and your route. In this case, you should rename that to something else.
 
-
 #### `cannot find module './chunks/xxxx.js'` error
 
 Dynamic imports in `instrumentation.ts` will cause this error at runtime. Remove dynamic imports to resolve.
@@ -75,24 +74,26 @@ The config recommended by Sentry docs uses dynamic imports in `instrumentation.t
 Here's a working Sentry config which resolves the error:
 
 `instrumentation.ts`
+
 ```typescript
-import * as Sentry from '@sentry/nextjs';
-import { initSentry } from '../sentry.server.config';
+import * as Sentry from "@sentry/nextjs";
+import { initSentry } from "../sentry.server.config";
 
 export const onRequestError = Sentry.captureRequestError;
 
 export async function register() {
-  initSentry(process.env.NEXT_RUNTIME as 'nodejs' | 'edge');
+  initSentry(process.env.NEXT_RUNTIME as "nodejs" | "edge");
 }
 ```
 
 `sentry.server.config.ts`
+
 ```typescript
-import * as Sentry from '@sentry/nextjs';
+import * as Sentry from "@sentry/nextjs";
 
-export const initSentry = (runtime: 'nodejs' | 'edge') => {
+export const initSentry = (runtime: "nodejs" | "edge") => {
   Sentry.init({
-    dsn: 'https://...',
+    dsn: "https://...",
 
     //...rest of your config
   });
diff --git a/pages/aws/config.mdx b/pages/aws/config.mdx
index f5cebda..bcee5d4 100644
--- a/pages/aws/config.mdx
+++ b/pages/aws/config.mdx
@@ -25,12 +25,12 @@ For more advanced use cases, you can check [how to implement custom overrides](/
 
 If you want to look at a full example, you can check [the full example](/aws/config/full_example).
 
-
 ### Opt out of default poweredByHeader
 
 By default Next.js will add the [`x-powered-by`](https://nextjs.org/docs/app/api-reference/config/next-config-js/poweredByHeader) header. OpenNext will also add a header `x-opennext`. To opt-out of this, open `next.config.js` and disable the poweredByHeader property in the configuration:
+
 ```ts
 module.exports = {
   poweredByHeader: false,
-}
-```
\ No newline at end of file
+};
+```
diff --git a/pages/aws/config/_meta.json b/pages/aws/config/_meta.json
index 61715fd..a2b2009 100644
--- a/pages/aws/config/_meta.json
+++ b/pages/aws/config/_meta.json
@@ -5,4 +5,4 @@
   "full_example": "Full Example",
   "nx": "Nx Monorepo",
   "overrides": "Overrides"
-}
\ No newline at end of file
+}
diff --git a/pages/aws/config/custom_overrides.mdx b/pages/aws/config/custom_overrides.mdx
index d255abb..0f1c66e 100644
--- a/pages/aws/config/custom_overrides.mdx
+++ b/pages/aws/config/custom_overrides.mdx
@@ -1,4 +1,4 @@
-import { Callout } from 'nextra/components'
+import { Callout } from "nextra/components";
 
 In some cases the simple example is not enough, and you want to add more customization to your server. This is where the lazy loaded overrides come in. You can override any part of the server by providing a function that returns a promise that resolves to the override object. This is useful when you want to add custom logic to your server, like adding a custom queue, or adding a custom converter.
 
@@ -19,135 +19,133 @@ You'll still have to use a fallback value during dev as this is not used by the
 
 ```ts
 // customConverter.ts
-import converter from '@opennextjs/aws/overrides/converters/aws-apigw-v2.js'
-import type { Converter } from '@opennextjs/aws/types/overrides.js'
-import { Config } from 'sst/node/Config'
-const mySecretKey = Config.YOUR_SECRET_KEY
+import converter from "@opennextjs/aws/overrides/converters/aws-apigw-v2.js";
+import type { Converter } from "@opennextjs/aws/types/overrides.js";
+import { Config } from "sst/node/Config";
+const mySecretKey = Config.YOUR_SECRET_KEY;
 
 export default {
   convertFrom: async (event) => {
-    const result = await converter.convertFrom(event)
+    const result = await converter.convertFrom(event);
     return {
       ...result,
       headers: {
         ...result.headers,
-        'inserted-in-converter': '1',
-        'my-super-secret-key': mySecretKey
-      }
-    }
+        "inserted-in-converter": "1",
+        "my-super-secret-key": mySecretKey,
+      },
+    };
   },
-  convertTo : async (intResult) => {
-    const result = await converter.convertTo(intResult)
+  convertTo: async (intResult) => {
+    const result = await converter.convertTo(intResult);
     return {
       ...result,
       headers: {
         ...result.headers,
-        'x-converter-end': '1'
-      }
-    }
+        "x-converter-end": "1",
+      },
+    };
   },
-  name: 'custom-apigw-v2'
-} as Converter
+  name: "custom-apigw-v2",
+} as Converter;
 ```
 
 ```ts
 // open-next.config.ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js'
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 
 const config = {
   default: {
     override: {
-      converter: () => import('./customConverter').then((mod) => mod.default)
-    }
-  }
-} as OpenNextConfig
+      converter: () => import("./customConverter").then((mod) => mod.default),
+    },
+  },
+} as OpenNextConfig;
 ```
 
 ## Custom wrapper
+
 Here we provide a few examples for some custom wrapper.
 
 ### Define a global to use node in the middleware
 
 ```ts
 // customWrapper.ts
-import defaultWrapper from '@opennextjs/aws/overrides/wrappers/aws-lambda.js'
+import defaultWrapper from "@opennextjs/aws/overrides/wrappers/aws-lambda.js";
 
 //Here you can define some globals
 declare global {
   var myApi: () => Promise<number>;
 }
 globalThis.myApi = async () => {
-  const crypto = await import('crypto')
+  const crypto = await import("crypto");
   return {
-    nb: crypto.randomInt(0, 100)
-  }
-}
+    nb: crypto.randomInt(0, 100),
+  };
+};
 
-export default defaultWrapper
+export default defaultWrapper;
 ```
 
 ```ts
 // open-next.config.ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js'
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {
     override: {
-      wrapper: () => import('./customWrapper').then((mod) => mod.default)
-    }
-  }
-} as OpenNextConfig
-export default config
+      wrapper: () => import("./customWrapper").then((mod) => mod.default),
+    },
+  },
+} as OpenNextConfig;
+export default config;
 ```
+
 But since Next dev server runs in a fake edge runtime and that the global is defined only for deployment, you'll have to mock the global in your middleware.
 
 ```ts
 // middleware.ts
-import { NextResponse } from 'next/server'
-import type { NextRequest } from 'next/server'
+import { NextResponse } from "next/server";
+import type { NextRequest } from "next/server";
 
 // Here you need to mock the global if not present
 // One way to avoid issues with different implementation would be to create an api endpoint
 // that uses the exact same logic as the global you defined earlier,
 // and that is only available during development i.e. /api/dev/myApi
-if(!globalThis.myApi) {
+if (!globalThis.myApi) {
   globalThis.myApi = async () => {
-    return await fetch('http://localhost:3000/api/dev/myApi').then(res => res.json())
-  }
+    return await fetch("http://localhost:3000/api/dev/myApi").then((res) => res.json());
+  };
 }
 
 export function middleware(request: NextRequest) {
   // You can also send an error in the api endpoint itself
   // Or you could add all the dev endpoint in their own lambda
   // that you do not deploy in production
-  if(request.nextUrl.pathname.startsWith('/api/dev') && process.env.NODE_ENV === 'production') {
-    return NextResponse('This route is only available in development',{
+  if (request.nextUrl.pathname.startsWith("/api/dev") && process.env.NODE_ENV === "production") {
+    return NextResponse("This route is only available in development", {
       status: 500,
-    })
+    });
   }
   // Now you can use Node.js in your middleware
-  const {nb} = await myApi()
+  const { nb } = await myApi();
 
   // ... your code here
 }
-
 ```
 
-
 ### Use middy.js with the wrapper
 
 ```ts
 // customWrapper.ts
-import streamingWrapper from '@opennextjs/aws/overrides/wrappers/aws-lambda.js'
-import type { WrapperHandler } from '@opennextjs/aws/types/overrides.js'
-import middy from '@middy/core'
-import httpSecurityHeaders from '@middy/http-security-headers'
-
-const handler : WrapperHandler = async (handler, converter) => {
-  const defaultHandler = await streamingWrapper.wrapper(handler, converter)
-  return middy()
-  .use(httpSecurityHeaders())
-  .handler(defaultHandler)
-}
+import streamingWrapper from "@opennextjs/aws/overrides/wrappers/aws-lambda.js";
+import type { WrapperHandler } from "@opennextjs/aws/types/overrides.js";
+import middy from "@middy/core";
+import httpSecurityHeaders from "@middy/http-security-headers";
+
+const handler: WrapperHandler = async (handler, converter) => {
+  const defaultHandler = await streamingWrapper.wrapper(handler, converter);
+  return middy().use(httpSecurityHeaders()).handler(defaultHandler);
+};
 
 export default {
   wrapper: handler,
@@ -158,15 +156,15 @@ export default {
 
 ```ts
 // open-next.config.ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js'
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {
     override: {
-      wrapper: () => import('./customWrapper').then((mod) => mod.default)
-    }
-  }
-} as OpenNextConfig
-export default config
+      wrapper: () => import("./customWrapper").then((mod) => mod.default),
+    },
+  },
+} as OpenNextConfig;
+export default config;
 ```
 
 ### Preload some routes during warmer event
@@ -175,30 +173,21 @@ In this example the custom wrapper is used to preload some important routes befo
 
 **WARNING**: This one is not properly tested. It's just an example of what you could do. You should test it properly before using it in production. Also preloading too many routes is probably a bad idea.
 
-
 ```ts
 // customWrapper.ts
-import type {
-  APIGatewayProxyEventV2,
-  APIGatewayProxyResultV2,
-} from "aws-lambda";
+import type { APIGatewayProxyEventV2, APIGatewayProxyResultV2 } from "aws-lambda";
 import { Writable } from "node:stream";
 
 import { WarmerEvent, WarmerResponse } from "@opennextjs/aws/adapters/warmer-function.js";
 import type { StreamCreator } from "@opennextjs/aws/types/open-next.js";
 import type { WrapperHandler } from "@opennextjs/aws/types/overrides.js";
 
-type AwsLambdaEvent =
-  | APIGatewayProxyEventV2
-  | WarmerEvent;
-
-type AwsLambdaReturn =
-  | APIGatewayProxyResultV2
-  | WarmerResponse;
+type AwsLambdaEvent = APIGatewayProxyEventV2 | WarmerEvent;
 
+type AwsLambdaReturn = APIGatewayProxyResultV2 | WarmerResponse;
 
-const serverId = Math.random().toPrecision(5).toString()
-let isPreloaded = false
+const serverId = Math.random().toPrecision(5).toString();
+let isPreloaded = false;
 
 function formatWarmerResponse(event: WarmerEvent) {
   return new Promise<WarmerResponse>((resolve) => {
@@ -211,30 +200,29 @@ function formatWarmerResponse(event: WarmerEvent) {
 const handler: WrapperHandler =
   async (handler, converter) =>
   async (event: AwsLambdaEvent): Promise<AwsLambdaReturn> => {
-    console.log('custom wrapper')
+    console.log("custom wrapper");
     // Handle warmer event
     if ("type" in event) {
-      if(!isPreloaded) {
+      if (!isPreloaded) {
         // You could preload every route you want here
         // Be careful, while the route is preloading the lambda cannot process other requests
         await handler({
-          type: 'core',
-          url: '/myRoute',
-          method: 'GET',
+          type: "core",
+          url: "/myRoute",
+          method: "GET",
           headers: {},
           query: {},
-          rawPath: '/myRoute',
+          rawPath: "/myRoute",
           cookies: {},
-          remoteAddress: ''
+          remoteAddress: "",
         });
-        isPreloaded = true
+        isPreloaded = true;
       }
       return formatWarmerResponse(event);
     }
 
-
     const internalEvent = await converter.convertFrom(event);
-    internalEvent.headers['inserted-in-wrapper'] = 'hello from wrapper'
+    internalEvent.headers["inserted-in-wrapper"] = "hello from wrapper";
 
     //This is a workaround, there is an issue in node that causes node to crash silently if the OpenNextNodeResponse stream is not consumed
     //This does not happen everytime, it's probably caused by suspended component in ssr (either via <Suspense> or loading.tsx)
@@ -251,7 +239,7 @@ const handler: WrapperHandler =
     };
 
     const response = await handler(internalEvent, fakeStream);
-    response.headers['x-wrapper'] = 'hi'
+    response.headers["x-wrapper"] = "hi";
 
     return converter.convertTo(response, event);
   };
@@ -265,14 +253,14 @@ export default {
 
 ```ts
 // open-next.config.ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js'
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {
     override: {
-      wrapper: () => import('./customWrapper').then((mod) => mod.default)
-    }
-  }
-} as OpenNextConfig
+      wrapper: () => import("./customWrapper").then((mod) => mod.default),
+    },
+  },
+} as OpenNextConfig;
 ```
 
 ## Custom Incremental cache
@@ -280,12 +268,12 @@ const config = {
 You can take inspiration from our [`fs-dev`](https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/overrides/incrementalCache/fs-dev.ts) override which uses the file system to store the incremental cache. You need an `open-next.config.ts` with this:
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.ts';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.ts";
 const config = {
   default: {
     override: {
       // can be any of our included ones or your own custom override
-      incrementalCache: () => import('./customIncrementalCache').then((mod) => mod.default),
+      incrementalCache: () => import("./customIncrementalCache").then((mod) => mod.default),
     },
   },
 } satisfies OpenNextConfig;
@@ -300,12 +288,12 @@ export default config;
 By default it will use SQS queue to revalidate stale routes. You can read more about this [here](/aws/config/overrides/queue). To create your own custom override you can take inspiration by looking at our [included](https://github.com/opennextjs/opennextjs-aws/tree/main/packages/open-next/src/overrides/queue) implementations. You need an `open-next.config.ts` with this:
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.ts';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.ts";
 const config = {
   default: {
     override: {
       // can be any of our included ones or your own custom override
-      queue: () => import('./customQueue').then((mod) => mod.default),
+      queue: () => import("./customQueue").then((mod) => mod.default),
     },
   },
 } satisfies OpenNextConfig;
@@ -320,12 +308,12 @@ export default config;
 To override the tag cache you can take inspiration by looking at the [`fs-dev`](https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/overrides/tagCache/fs-dev.ts) override that uses the filesystem. You can read more about this override [here](/aws/config/overrides/tag_cache). You need an `open-next.config.ts` with this:
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.ts';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.ts";
 const config = {
   default: {
     override: {
       // can be any of our included ones or your own custom override
-      tagCache: () => import('./customTagCache').then((mod) => mod.default),
+      tagCache: () => import("./customTagCache").then((mod) => mod.default),
     },
   },
 } satisfies OpenNextConfig;
@@ -340,14 +328,14 @@ export default config;
 This override is only used internally by OpenNext to resolve the origin of the request if you have an `external` middleware. You can take inspiration from looking at our included [`pattern-env`](https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/overrides/originResolver/pattern-env.ts) override. You need an `open-next.config.ts` with this:
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {},
   middleware: {
     // must be true for the originResolver to be used
     external: true,
     // can be any of our included ones or your own custom override
-    originResolver: () => import('./customOriginResolver').then((mod) => mod.default),
+    originResolver: () => import("./customOriginResolver").then((mod) => mod.default),
   },
 } satisfies OpenNextConfig;
 
@@ -361,11 +349,11 @@ export default config;
 This override is used in the image optimization server to load an image from a custom source. You can look at our implemention of using the file system [here](https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/overrides/imageLoader/fs-dev.ts). You need an `open-next.config.ts` with this:
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {},
   imageOptimization: {
-    loader: () => import('./customImageLoader').then((mod) => mod.default),
+    loader: () => import("./customImageLoader").then((mod) => mod.default),
   },
 } satisfies OpenNextConfig;
 
@@ -379,11 +367,11 @@ export default config;
 To have a custom override for the warmer invoke you can take inspiration by looking at our [`aws-lambda`](https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/overrides/warmer/aws-lambda.ts) override. You need an `open-next.config.ts` with this:
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {},
   warmer: {
-    invokeFunction: () => import('./customWarmer').then((mod) => mod.default),
+    invokeFunction: () => import("./customWarmer").then((mod) => mod.default),
   },
 } satisfies OpenNextConfig;
 
@@ -397,12 +385,12 @@ export default config;
 To have a custom override for the CDN Invalidation you can take inspiration by looking at our [`cloudfront`](https://github.com/opennextjs/opennextjs-aws/tree/main/packages/open-next/src/overrides/cdnInvalidation/cloudfront.ts) override. You need an `open-next.config.ts` with this:
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {
     override: {
-      cdnInvalidation: () => import('./customCdnInvalidation').then((mod) => mod.default),
-    }
+      cdnInvalidation: () => import("./customCdnInvalidation").then((mod) => mod.default),
+    },
   },
 } satisfies OpenNextConfig;
 
@@ -416,12 +404,12 @@ export default config;
 This is used by OpenNext to proxy rewritten requests to external services. You can read more about it [here](/aws/config/overrides/proxy_external_request). To have a custom override for the External Request Proxy you can take inspiration by looking at our [`fetch`](https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/overrides/proxyExternalRequest/fetch.ts) override. You need an `open-next.config.ts` with this:
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {
     override: {
-      proxyExternalRequest: () => import('./customProxyExternalRequest').then((mod) => mod.default),
-    }
+      proxyExternalRequest: () => import("./customProxyExternalRequest").then((mod) => mod.default),
+    },
   },
 } satisfies OpenNextConfig;
 
diff --git a/pages/aws/config/full_example.mdx b/pages/aws/config/full_example.mdx
index b99e963..fd45da4 100644
--- a/pages/aws/config/full_example.mdx
+++ b/pages/aws/config/full_example.mdx
@@ -5,7 +5,7 @@ Here is a detailed example of an `open-next.config.ts` file. This file need to b
 For more information about the options here, take a look at the [reference section](/aws/config/reference).
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next";
 const config = {
   default: {
     // This is the default server, similar to the server-function in open-next v2
@@ -13,14 +13,14 @@ const config = {
     // for normal lambda as in open-next v2
     override: {
       // This is necessary to enable lambda streaming, defaults to aws-lambda
-      wrapper: 'aws-lambda-streaming',
+      wrapper: "aws-lambda-streaming",
       // Convert the input and output of the server, defaults to aws-apigw-v2
-      converter: 'aws-apigw-v2',
+      converter: "aws-apigw-v2",
       // Used for fetch cache and html/rsc/json cache, defaults to s3
-      incrementalCache: 's3',
+      incrementalCache: "s3",
       // Used for external rewrites, defaults to node
-      proxyExternalRequest: 'node',
-      tagCache: 'dynamodb', // Used for revalidatePath and revalidateTag, defaults to dynamodb
+      proxyExternalRequest: "node",
+      tagCache: "dynamodb", // Used for revalidatePath and revalidateTag, defaults to dynamodb
       // You can override any part that is a `LazyLoadedOverride` this way
       queue: () =>
         Promise.resolve({
@@ -33,8 +33,8 @@ const config = {
     // only for example purposes, you most likely should not use this
     // this can be used on every server to install additional packages
     install: {
-      packages: ['sharp@0.33.5'],
-      arch: 'arm64',
+      packages: ["sharp@0.33.5"],
+      arch: "arm64",
     },
     minify: true, // This will minify the output
   },
@@ -43,18 +43,18 @@ const config = {
   functions: {
     ssr: {
       routes: [
-        'app/api/isr/route',
-        'app/api/sse/route',
-        'app/api/revalidateTag/route', // app dir Api routes
-        'app/route1/page',
-        'app/route2/page', // app dir pages
-        'pages/route3', // page dir pages
+        "app/api/isr/route",
+        "app/api/sse/route",
+        "app/api/revalidateTag/route", // app dir Api routes
+        "app/route1/page",
+        "app/route2/page", // app dir pages
+        "pages/route3", // page dir pages
       ], // For app dir, you need to include route|page, no need to include layout or loading
       // patterns needs to be in a cloudfront compatible format
       // this will be used to generate the output
-      patterns: ['api/*', 'route1', 'route2', 'route3'],
+      patterns: ["api/*", "route1", "route2", "route3"],
       override: {
-        wrapper: 'aws-lambda-streaming',
+        wrapper: "aws-lambda-streaming",
       },
       // This enables the bundled next server which is faster and reduce the size of the server
       // This is also experimental and might not work in all cases
@@ -63,22 +63,22 @@ const config = {
     pageSsr: {
       // For page dir routes should be in the form `pages/${route}` without the extension
       // It should match the filesystem
-      routes: ['pages/pageSsr'],
+      routes: ["pages/pageSsr"],
       // BUILD_ID is a special case, it will be replaced with the actual build id
-      patterns: ['pageSsr', '_next/data/BUILD_ID/pageSsr.json'],
+      patterns: ["pageSsr", "_next/data/BUILD_ID/pageSsr.json"],
       override: {
-        wrapper: 'node',
-        converter: 'node',
-        // This is necessary to generate the dockerfile and 
+        wrapper: "node",
+        converter: "node",
+        // This is necessary to generate the dockerfile and
         // for the implementation to know that it needs to deploy on docker
         // You can also provide a string here which will be used to create the dockerfile
         generateDockerfile: true,
       },
     },
     edge: {
-      runtime: 'edge',
-      routes: ['app/ssr/page'],
-      patterns: ['ssr'],
+      runtime: "edge",
+      routes: ["app/ssr/page"],
+      patterns: ["ssr"],
       override: {},
     },
   },
@@ -99,34 +99,34 @@ const config = {
     // You can customize this to your needs
     // By default it will install with these options:
     install: {
-      packages: ['sharp@0.32.6'],
-      arch: 'arm64',
-      nodeVersion: '18',
-      libc: 'glibc',
+      packages: ["sharp@0.32.6"],
+      arch: "arm64",
+      nodeVersion: "18",
+      libc: "glibc",
     },
   },
   // Initialization function is a special server that will run at build time to initialize the cache.
   // By default, it only initializes the tag cache. Besides the common options, you can use the following options:
   initializationFunction: {
-    tagCache: 'dynamodb-lite', // Can be overridden with a LazyLoadedOverride
+    tagCache: "dynamodb-lite", // Can be overridden with a LazyLoadedOverride
   },
   // Override the default revalidate function
   // By default, works for lambda and on SQS event.
   // Supports only node runtime
   revalidate: {
     override: {
-      wrapper: 'aws-lambda', // Can be overridden with a LazyLoadedOverride
-      converter: 'aws-apigw-v2', // Can be overridden with a LazyLoadedOverride
+      wrapper: "aws-lambda", // Can be overridden with a LazyLoadedOverride
+      converter: "aws-apigw-v2", // Can be overridden with a LazyLoadedOverride
     },
   },
   // Override the default warmer
   // By default, works for lambda only.
   // If you override this, you'll need to handle the warmer event in the wrapper
   warmer: {
-    invokeFunction: 'aws-lambda', // Can be overridden with a LazyLoadedOverride
+    invokeFunction: "aws-lambda", // Can be overridden with a LazyLoadedOverride
     override: {
-      wrapper: 'aws-lambda', // Can be overridden with a LazyLoadedOverride
-      converter: 'aws-apigw-v2', // Can be overridden with a LazyLoadedOverride
+      wrapper: "aws-lambda", // Can be overridden with a LazyLoadedOverride
+      converter: "aws-apigw-v2", // Can be overridden with a LazyLoadedOverride
     },
   },
   // If you want to override the default build command, you can do it here
@@ -149,22 +149,22 @@ const config = {
     // This is executed for every request and after next config headers and middleware has executed.
     // Here is a very simple example of how you can use it:
     headersAndCookiesPriority: (event) => {
-      if (event.rawPath.startsWith('/api')) {
-        return 'middleware';
+      if (event.rawPath.startsWith("/api")) {
+        return "middleware";
       }
-      return 'handler';
+      return "handler";
     },
   },
-  // The path to the target folder of build output from the `buildCommand` option 
+  // The path to the target folder of build output from the `buildCommand` option
   // (the path which will contain the `.next` and `.open-next` folders).
   // This path is relative from the current process.cwd() - Optional defaults to "."
-  buildOutputPath: 'build',
+  buildOutputPath: "build",
   // The path to the root of the Next.js app's source code.
   // This path is relative from the current process.cwd(). - Optional defaults to "."
-  appPath: 'app',
-  // The path to the package.json file of the Next.js app. 
+  appPath: "app",
+  // The path to the package.json file of the Next.js app.
   // This path is relative from the current process.cwd(). - Optional
-  packageJsonPath: 'package.json',
+  packageJsonPath: "package.json",
   // Advanced usage
   // If you use the edge runtime somewhere (either with an external middleware or in the functions), we compile 2 versions of the open-next.config.ts file.
   // One for the node runtime and one for the edge runtime.
@@ -174,4 +174,4 @@ const config = {
 } satisfies OpenNextConfig;
 
 export default config;
-```
\ No newline at end of file
+```
diff --git a/pages/aws/config/nx.mdx b/pages/aws/config/nx.mdx
index e9334a8..b635c24 100644
--- a/pages/aws/config/nx.mdx
+++ b/pages/aws/config/nx.mdx
@@ -1,9 +1,11 @@
 # Configuring OpenNext for use in an Nx Monorepo.
+
 Here's a detailed exampled of how to add OpenNext + SST to an existing Nx workspace, with an existing NextJS application sitting at `apps/next-site`
 
 1. install `open-next`: `pnpm add —save-dev @opennextjs/aws`
 
 2. Update your `apps/next-site/next.config.js` add `output: ‘standalone’`, and you want to add `experimental.outputFileTracingRoot`, it should look a little like this:
+
 ```javascript
 //@ts-check
 
@@ -36,6 +38,7 @@ module.exports = composePlugins(...plugins)(nextConfig);
 ```
 
 3. Create `open-next.config.ts` inside your apps root directory, it should look a little something like this:
+
 ```javascript
 import type { OpenNextConfig } from '@opennextjs/aws/types/open-next';
 
@@ -57,6 +60,7 @@ it might even work.
 
 However, we don't want to rely on needing to manually running a build every time we want to deploy a change, so instead we can set up a target.
 We do this in your project's `project.json` (in this case, living at `apps/next-site/project`), we want to find the targets object and update it:
+
 ```diff
 {
   "name": "next-site",
@@ -79,7 +83,9 @@ We do this in your project's `project.json` (in this case, living at `apps/next-
 }
 
 ```
+
 Next we need to add the open-next directory to our eslint's `ignorePatterns` array
+
 ```diff
 {
   "extends": [
@@ -134,21 +140,21 @@ but we will not use the SST cli to init this project, because it wants to add a
 export default $config({
   app(input) {
     return {
-      name: 'next-site', // use whatever your project is called here
-      removal: input?.stage === 'production' ? 'retain' : 'remove',
-      home: 'aws',
+      name: "next-site", // use whatever your project is called here
+      removal: input?.stage === "production" ? "retain" : "remove",
+      home: "aws",
     };
   },
   async run() {
-    new sst.aws.Nextjs('Site', {
-      buildCommand: 'exit 0;' // again, we want to get Nx to handle building
+    new sst.aws.Nextjs("Site", {
+      buildCommand: "exit 0;", // again, we want to get Nx to handle building
     });
   },
 });
-
 ```
 
 - now, you probably see some type errors, as SST is not initialized yet, but we can resolve this by running
+
 ```bash
 $ cd apps/next-site && sst install
 ```
@@ -245,8 +251,9 @@ this will resolve the type issues and initialise SST.
 ```
 
 now we can run (or if you want a custom stage, you can simply do `nx deploy next-site --stage this-is-my-stage` and it will be passed directly to the sst command).
+
 ```bash
 $ nx deploy next-site --configuration dev # using dev configuration (which sets the stage to development)
 # nx deploy next-site -c dev # OR
 # nx deploy next-site --stage my-stage # Custom Stage
-```
\ No newline at end of file
+```
diff --git a/pages/aws/config/overrides/_meta.json b/pages/aws/config/overrides/_meta.json
index 5e89222..36719ab 100644
--- a/pages/aws/config/overrides/_meta.json
+++ b/pages/aws/config/overrides/_meta.json
@@ -9,4 +9,4 @@
   "origin_resolver": "Origin Resolver",
   "invoke_function": "Invoke Function for the warmer",
   "automatic_cdn_invalidation": "Automatic CDN Invalidation"
-}
\ No newline at end of file
+}
diff --git a/pages/aws/config/overrides/automatic_cdn_invalidation.mdx b/pages/aws/config/overrides/automatic_cdn_invalidation.mdx
index dc08370..c9a9c09 100644
--- a/pages/aws/config/overrides/automatic_cdn_invalidation.mdx
+++ b/pages/aws/config/overrides/automatic_cdn_invalidation.mdx
@@ -1,4 +1,4 @@
-import {Callout} from 'nextra/components'
+import { Callout } from "nextra/components";
 
 Available since `@opennextjs/aws` 3.4.0
 
@@ -25,10 +25,11 @@ This implementation will send an invalidation request for every route that needs
 Tag cache invalidation could end up triggering thousands of invalidation requests.
 
 Only use this implementation if you are aware of the costs and are willing to pay for it.
+
 </Callout>
 
 The CloudFront Automatic CDN Invalidation will invalidate the cache of the CloudFront distribution.
 
 ##### Requirements
 
-- You need to provide the `CLOUDFRONT_DISTRIBUTION_ID` environment variable to your server.
\ No newline at end of file
+- You need to provide the `CLOUDFRONT_DISTRIBUTION_ID` environment variable to your server.
diff --git a/pages/aws/config/overrides/converter.mdx b/pages/aws/config/overrides/converter.mdx
index b8e5d77..b23346d 100644
--- a/pages/aws/config/overrides/converter.mdx
+++ b/pages/aws/config/overrides/converter.mdx
@@ -3,6 +3,7 @@ This override is meant to convert request and response provided from your wrappe
 If you want to better understand how to implement your own Converter, the easiest way would be to take a look at one of the existing [included Converter](https://github.com/opennextjs/opennextjs-aws/tree/main/packages/open-next/src/overrides/converters)
 
 Couple of things to note :
+
 - If you use a `StreamCreator` in your wrapper, you probably don't need to do anything in the `convertTo` function.
 - If used for the default, the image optimization, or one of the splitted server the internal types will be `InternalEvent` and `InternalResult` respectively.
 - If used for the external middleware, the internal types will be `InternalEvent` and `InternalResult | MiddlewareResult` respectively.
@@ -36,4 +37,4 @@ The `sqs-revalidate` Converter is a converter for the Revalidation server. It us
 
 ### dummy
 
-The `dummy` Converter is a dummy implementation that will just forward the request and response as is.
\ No newline at end of file
+The `dummy` Converter is a dummy implementation that will just forward the request and response as is.
diff --git a/pages/aws/config/overrides/image_loader.mdx b/pages/aws/config/overrides/image_loader.mdx
index 06256a1..9a89d90 100644
--- a/pages/aws/config/overrides/image_loader.mdx
+++ b/pages/aws/config/overrides/image_loader.mdx
@@ -21,7 +21,7 @@ The `s3-lite` ImageLoader will load images from an S3 bucket. It uses the `aws4f
 
 ##### Requirements
 
-- You need to provide the `BUCKET_KEY_PREFIX`, `BUCKET_NAME` environment variables to your server. 
+- You need to provide the `BUCKET_KEY_PREFIX`, `BUCKET_NAME` environment variables to your server.
 - Can also provide `BUCKET_REGION`. It fallbacks to `AWS_REGION` ?? `AWS_DEFAULT_REGION`. This should be set by AWS automatically. You can read more about how this works on AWS Lambdas [here](https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html#configuration-envvars-runtime).
 
 ### host
@@ -39,4 +39,4 @@ The FsDev ImageLoader is a simple implementation that loads images from the `.op
 
 ### dummy
 
-The Dummy ImageLoader is a dummy implementation that will throw an exception. It should not be used.
\ No newline at end of file
+The Dummy ImageLoader is a dummy implementation that will throw an exception. It should not be used.
diff --git a/pages/aws/config/overrides/incremental_cache.mdx b/pages/aws/config/overrides/incremental_cache.mdx
index 0e9ca3d..e0cbc31 100644
--- a/pages/aws/config/overrides/incremental_cache.mdx
+++ b/pages/aws/config/overrides/incremental_cache.mdx
@@ -1,4 +1,4 @@
-import { Callout } from 'nextra/components';
+import { Callout } from "nextra/components";
 
 This override is used by the [`cache` adapter](https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/adapters/cache.ts) that is provided by OpenNext to the NextServer. It is also used by OpenNext if `enableCacheInterception` is set to `true` in the configuration.
 
@@ -47,20 +47,23 @@ It needs to run on the local filesystem, and expect to be run from the OpenNext
 Because of how it works, this implementation is only eventually consistent and errors during update could cause inconsistencies between the local cache in some instances and the S3 cache.
 
 It could also end up being slower (and more expensive) than simpler implementations if used in a low traffic serverless environment.
+
 </Callout>
 
-The MultiTierDdbS3 IncrementalCache is a more complex implementation. 
+The MultiTierDdbS3 IncrementalCache is a more complex implementation.
 Cache are stored in a local In Memory LRU cache as well as in S3. DynamoDB is used to keep local cache in sync between multiple instances of the server.
 It uses `aws4fetch` to interact with S3 and DynamoDB.
 
 ##### How does it work
 
 On get :
+
 1. When a cache is requested, it first checks the local cache. If the cache is not found, it will fetch it from S3 and store it in the local cache.
 2. If the local cache exist for this key, it will check metadata in DynamoDB to see if the cache is still valid. If it is not, it will fetch the cache from S3 and store it in the local cache.
 3. If the local cache is valid, it will return it.
 
 On update :
+
 1. When a cache is updated, it will first try to update the cache in S3.
 2. If the update is successful, it will update the metadata in DynamoDB.
 3. Finally, it will update the local cache.
@@ -68,4 +71,4 @@ On update :
 ##### Requirements
 
 - You need to provide the `CACHE_BUCKET_REGION`, `CACHE_BUCKET_KEY_PREFIX`, `CACHE_BUCKET_NAME`, `CACHE_DYNAMO_TABLE`, `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and `AWS_SESSION_TOKEN`, `OPEN_NEXT_LOCAL_CACHE_TTL_MS` (optional), `OPEN_NEXT_LOCAL_CACHE_SIZE`(optional) environment variables to your server.
-- DynamoDB table should have a primary key `path` of type `String` and a sort key `tag` of type `String`. (It can reuse the same table as the one used by the default `tagCache`)
\ No newline at end of file
+- DynamoDB table should have a primary key `path` of type `String` and a sort key `tag` of type `String`. (It can reuse the same table as the one used by the default `tagCache`)
diff --git a/pages/aws/config/overrides/origin_resolver.mdx b/pages/aws/config/overrides/origin_resolver.mdx
index 09737cc..45fa536 100644
--- a/pages/aws/config/overrides/origin_resolver.mdx
+++ b/pages/aws/config/overrides/origin_resolver.mdx
@@ -3,4 +3,4 @@ This is only used by the external middleware.
 
 At build time, we may not know where the splitted server will be deployed, so we need to resolve the origin at runtime. This is why we need this override. The origin is resolved by this override will need to be handled by the wrapper used. At the moment, only the `aws-cloudfront` and the `cloudflare-edge` wrapper are able to do so.
 
-If you want to better understand how to implement your own OriginResolver, the easiest way would be to take a look at the existing [included OriginResolver](https://github.com/opennextjs/opennextjs-aws/tree/main/packages/open-next/src/overrides/originResolver).
\ No newline at end of file
+If you want to better understand how to implement your own OriginResolver, the easiest way would be to take a look at the existing [included OriginResolver](https://github.com/opennextjs/opennextjs-aws/tree/main/packages/open-next/src/overrides/originResolver).
diff --git a/pages/aws/config/overrides/proxy_external_request.mdx b/pages/aws/config/overrides/proxy_external_request.mdx
index 641cb38..3f57935 100644
--- a/pages/aws/config/overrides/proxy_external_request.mdx
+++ b/pages/aws/config/overrides/proxy_external_request.mdx
@@ -14,4 +14,4 @@ This uses fetch to proxy the request to the external service. It doesn't work in
 
 ### dummy
 
-This is a dummy implementation that throws a FatalError.
\ No newline at end of file
+This is a dummy implementation that throws a FatalError.
diff --git a/pages/aws/config/overrides/queue.mdx b/pages/aws/config/overrides/queue.mdx
index de99266..c4d2961 100644
--- a/pages/aws/config/overrides/queue.mdx
+++ b/pages/aws/config/overrides/queue.mdx
@@ -1,4 +1,4 @@
-import {Callout} from 'nextra/components'
+import { Callout } from "nextra/components";
 
 This override is used by OpenNext to trigger the revalidation of stale routes.
 Before sending the response to the client, OpenNext will check if the route is stale and if it is, it will call the queue override to revalidate the route.
@@ -6,6 +6,7 @@ Before sending the response to the client, OpenNext will check if the route is s
 If you want to better understand how to implement your own Queue, the easiest way would be to take a look at the existing [included Queue](https://github.com/opennextjs/opennextjs-aws/tree/main/packages/open-next/src/overrides/queue).
 
 Couple of things to note :
+
 - The default implementation use an SQS queue. This has the main advantage of being able to control the concurrency of the revalidations as well as avoiding trigerring the revalidation multiple times for the same route.
 - You don't have to use a queue at all. You could trigger the revalidation directly in the Queue override itself. You can see a very simple implementation of this [in the `direct` override](https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/overrides/queue/direct.ts).
 
@@ -33,10 +34,10 @@ This implementation is a lighter version of the `sqs` Queue as it uses `aws4fetc
 
 The Direct Queue will directly trigger the revalidation of the route in the Queue override itself. It is useful for development purposes and when you don't want to use a queue.
 
-<Callout type='warning'>
-Be careful with this implementation as it could lead to multiple revalidations of the same route.
+<Callout type="warning">
+  Be careful with this implementation as it could lead to multiple revalidations of the same route.
 </Callout>
 
 ### dummy
 
-The Dummy Queue is a dummy implementation that will throw an exception. It should not be used unless you want to disable ISR.
\ No newline at end of file
+The Dummy Queue is a dummy implementation that will throw an exception. It should not be used unless you want to disable ISR.
diff --git a/pages/aws/config/overrides/wrapper.mdx b/pages/aws/config/overrides/wrapper.mdx
index 6fbd086..33543a3 100644
--- a/pages/aws/config/overrides/wrapper.mdx
+++ b/pages/aws/config/overrides/wrapper.mdx
@@ -3,12 +3,12 @@ This is the main entrypoint of the server. It is used for every server and allow
 If you want to better understand how to implement your own Wrapper, the easiest way would be to take a look at one of the existing [included Wrapper](https://github.com/opennextjs/opennextjs-aws/tree/main/packages/open-next/src/overrides/wrappers).
 
 Couple of things to note :
+
 - If you want to use streaming (for the `node` runtime of next), you'll need to create a `StreamCreator` and pass it to the `handler`. You can find some example in the [node](https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/overrides/wrappers/node.ts) or [aws-lambda-streaming](https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/overrides/wrappers/aws-lambda-streaming.ts) wrapper.
 - If you don't use streaming (like in the default `aws-lambda` wrapper), you may still need to provide a fake `StreamCreator` to the `handler` to avoid a weird issue with Node itself (see [here](https://github.com/opennextjs/opennextjs-aws/blob/f685ddea8f8a5c82591dc02713aff7138f2d9896/packages/open-next/src/overrides/wrappers/aws-lambda.ts#L49-L65) for an example and a more thorough explanation).
 - If you use the `edge` runtime of Next (either for the external middleware or for an `edge` route or page), you don't need the `StreamCreator` at all.
 - If you are in a serverless environment and it supports `waitUntil`, you should define it here(see [here](https://github.com/opennextjs/opennextjs-aws/blob/b0b1f7776b41612d2638a33e3c9ced8c42afab0a/packages/open-next/src/overrides/wrappers/cloudflare-node.ts#L80). This might not be necessary depending on where you run it (for example the `aws-lambda-streaming` or the `node` wrapper doesn't need it.)
 
-
 ## Included Wrappers
 
 ### aws-lambda
@@ -16,6 +16,7 @@ Couple of things to note :
 The `aws-lambda` Wrapper is the default wrapper for AWS Lambda. It is used by default if you don't provide any Wrapper in your configuration.
 
 #### Features
+
 - [ ] Streaming
 - [ ] Proper support for `waitUntil`
 
@@ -24,6 +25,7 @@ The `aws-lambda` Wrapper is the default wrapper for AWS Lambda. It is used by de
 The `aws-lambda-streaming` Wrapper is a wrapper that allows you to use streaming in AWS Lambda. Streaming must be enabled for this lambda.
 
 #### Features
+
 - [x] Streaming
 - [x] Proper support for `waitUntil`
 
@@ -32,6 +34,7 @@ The `aws-lambda-streaming` Wrapper is a wrapper that allows you to use streaming
 The `cloudflare-edge` Wrapper is the wrapper for Cloudflare Workers. It should be used for the external middleware and for the `edge` runtime of Next.
 
 #### Features
+
 - [x] Streaming
 - [x] Proper support for `waitUntil`
 
@@ -40,6 +43,7 @@ The `cloudflare-edge` Wrapper is the wrapper for Cloudflare Workers. It should b
 The `cloudflare-node` Wrapper is the wrapper for Cloudflare Workers. It should be used only with the `node` runtime of Next and if you use `@opennextjs/cloudflare`.
 
 #### Features
+
 - [x] Streaming
 - [x] Proper support for `waitUntil`
 
@@ -48,6 +52,7 @@ The `cloudflare-node` Wrapper is the wrapper for Cloudflare Workers. It should b
 The `node` Wrapper is the wrapper for classic Node.js Server. This one is a long running server.
 
 #### Features
+
 - [x] Streaming
 - [x] Proper support for `waitUntil`
 
@@ -56,6 +61,7 @@ The `node` Wrapper is the wrapper for classic Node.js Server. This one is a long
 The `express-dev` Wrapper is the wrapper for a classic Express server. It is a long running process and should be used for development purposes only.
 
 #### Features
+
 - [x] Streaming
 - [x] Proper support for `waitUntil`
 
@@ -64,5 +70,6 @@ The `express-dev` Wrapper is the wrapper for a classic Express server. It is a l
 The `dummy` Wrapper is a dummy implementation that will just forward the event and `StreamCreator` to the handler.
 
 #### Features
+
 - [ ] Streaming
-- [ ] Proper support for `waitUntil`
\ No newline at end of file
+- [ ] Proper support for `waitUntil`
diff --git a/pages/aws/config/reference.mdx b/pages/aws/config/reference.mdx
index 99e20da..880d136 100644
--- a/pages/aws/config/reference.mdx
+++ b/pages/aws/config/reference.mdx
@@ -1,27 +1,26 @@
 Every option that you can use in `open-next.config.ts` will be listed here. This is the configuration file that you can use to customize the build.
 You can look at the [full example](full_example) to see how you can use these options.
 
-<br/>
+<br />
 
-import { Tabs } from 'nextra/components'
+import { Tabs } from "nextra/components";
 
 <Tabs items={['Server Options', 'General Build Options']}>
 <Tabs.Tab>
   Servers here refers to all the different build outputs (Lambda, Node, Deno etc). Each server can have its own options. This also includes some server/function that only need to run at build time.
 
-  Each server config will be under it's own key in the config object. Here are all the servers that you can configure:
+Each server config will be under it's own key in the config object. Here are all the servers that you can configure:
 
-  - Default Server - Key: `default` This is the default server, similar to the server-function in open-next v2
-  - Splitted Server - Key: `functions` This is only used if you want to split the server into multiple servers. This is a special case, under this key you will define every splitted server.
-  - External middleware - Key: `middleware` If you want to deploy your middleware separately from the default servers or functions, you can use this key.
-  - Revalidate Function - Key: `revalidate` This is a special server that will handle the revalidation queue.
-  - Image Optimization Server - Key: `imageOptimization` This server will handle `_next/image` optimization.
-  - Warmer Function - Key: `warmer` This server is meant to be used as a warmer for the lambda function.
-  - Initialization Function - Key: `initializationFunction` This is a special server that will run at build time to initialize the cache. By default it only initialize the tag cache.
-
-  <Tabs items={['Common Options','Default Server', 'Splitted Server', 'External middleware','Image Optimization server', 'Revalidate function', 'Warmer function', 'Initialization Function']}>
-    <Tabs.Tab>
+- Default Server - Key: `default` This is the default server, similar to the server-function in open-next v2
+- Splitted Server - Key: `functions` This is only used if you want to split the server into multiple servers. This is a special case, under this key you will define every splitted server.
+- External middleware - Key: `middleware` If you want to deploy your middleware separately from the default servers or functions, you can use this key.
+- Revalidate Function - Key: `revalidate` This is a special server that will handle the revalidation queue.
+- Image Optimization Server - Key: `imageOptimization` This server will handle `_next/image` optimization.
+- Warmer Function - Key: `warmer` This server is meant to be used as a warmer for the lambda function.
+- Initialization Function - Key: `initializationFunction` This is a special server that will run at build time to initialize the cache. By default it only initialize the tag cache.
 
+<Tabs items={['Common Options','Default Server', 'Splitted Server', 'External middleware','Image Optimization server', 'Revalidate function', 'Warmer function', 'Initialization Function']}>
+  <Tabs.Tab>
       All these servers share some common options that you can use to customize them.
 
       ### `minify`
@@ -38,7 +37,7 @@ import { Tabs } from 'nextra/components'
 
       #### [`wrapper`](overrides/wrapper)
 
-      This is the entrypoint of the server. 
+      This is the entrypoint of the server.
       Be aware that it might not be enough to change this to make it work on said platform. This is only the entrypoint, you might need to change other parts of the server to make it work on the platform.
 
       Possible values are: `aws-lambda`, `aws-lambda-streaming`, `cloudflare-edge`, `cloudflare-node`, `node`, `express-dev`, `dummy` or a `LazyLoadedOverride` that will return the wrapper.
@@ -81,23 +80,24 @@ import { Tabs } from 'nextra/components'
       Additional arguments to pass to the install command (npm install). It is a string that will get appended to the `npm install` command.
 
       Here is an example of how to install sharp on your default server function with ARM64 architecture:
+
       ```ts
       import type { OpenNextConfig } from '@opennextjs/aws/types/open-next';
       const config = {
-        default: {
-          install: {
-            packages: ['sharp@0.33.5'],
-            arch: 'arm64',
-          },
+      default: {
+        install: {
+          packages: ['sharp@0.33.5'],
+          arch: 'arm64',
         },
+      },
       } satisfies OpenNextConfig;
 
       export default config;
       ```
 
+  </Tabs.Tab>
 
-    </Tabs.Tab>
-    <Tabs.Tab>
+  <Tabs.Tab>
       ### `runtime`
 
       Runtime used for the server. The default server only support `node` or `deno`.
@@ -110,7 +110,7 @@ import { Tabs } from 'nextra/components'
       ### `placement`
 
       Option to determine where the server will be deployed. On a single region or on multiple regions at the edge.
-      
+
       This options does not have any effect on the build output, but is just an indication for IAC tools to know where to deploy the server.
 
       Possible values are: `regional`, `global`
@@ -118,7 +118,7 @@ import { Tabs } from 'nextra/components'
       ### `experimentalBundledNextServer`
       Bundle Next server into a single file.
       This results in a way smaller bundle but it might break for some cases.
-      
+
       This option is deprecated and doesn't work for Next 14.2+.
 
       ### `override`
@@ -151,11 +151,13 @@ import { Tabs } from 'nextra/components'
 
       #### [`cdnInvalidation`](overrides/automatic_cdn_invalidation)
 
-      Add possibility to override the CDN invalidation override. Used for on-demand invalidation with `revalidatePath()`, `revalidateTag()` and `res.revalidate()`. 
+      Add possibility to override the CDN invalidation override. Used for on-demand invalidation with `revalidatePath()`, `revalidateTag()` and `res.revalidate()`.
 
       Possible values are: `cloudfront`, `dummy` or a `LazyLoadedOverride` that will return the invalidatePaths. This override is disabled by default.
-    </Tabs.Tab>
-    <Tabs.Tab>
+
+  </Tabs.Tab>
+
+  <Tabs.Tab>
       Every splitted server will have the same options as the default server. In addition to that, you can use the following options:
 
       ### `routes` - Mandatory
@@ -177,15 +179,16 @@ import { Tabs } from 'nextra/components'
       For example:
       ```ts
       patterns: [
-        // This one will match all the routes that start with /api/
-        "/api/*",
-        // For a single route, this one will only match /page
-        "/page",
+      // This one will match all the routes that start with /api/
+      "/api/*",
+      // For a single route, this one will only match /page
+      "/page",
       ]
       ```
 
-    </Tabs.Tab>
-    <Tabs.Tab>
+  </Tabs.Tab>
+
+  <Tabs.Tab>
       ### `external` - Mandatory
       Only possible value is true. This is used to specify that this server is an external middleware.
 
@@ -196,21 +199,25 @@ import { Tabs } from 'nextra/components'
       ### [`originResolver`](overrides/origin_resolver)
 
       Origin resolver is used to resolve the origin for internal rewrite. By default, it uses the pattern-env origin resolver.
-      
+
       Possible values are: `pattern-env`, `dummy` or a `LazyLoadedOverride` that will return the origin resolver.
-    </Tabs.Tab>
-    <Tabs.Tab>
+
+  </Tabs.Tab>
+
+  <Tabs.Tab>
       Image optimization server is a special server that will handle the `_next/image` optimization. Besides the common options, you can use the following options:
 
       ### [`loader`](overrides/image_loader)
       The image loader is used to load the image from the source.
 
       Possible values are: `s3`, `s3-lite`, `host`, `fs-dev`, `dummy` or a `LazyLoadedOverride` that will return the loader.
-    </Tabs.Tab>
-    <Tabs.Tab>
-      Revalidate doesn't have any specific options. It only uses the common options.
-    </Tabs.Tab>
-    <Tabs.Tab>
+
+  </Tabs.Tab>
+
+<Tabs.Tab>Revalidate doesn't have any specific options. It only uses the common options.</Tabs.Tab>
+
+  <Tabs.Tab>
+
       Warmer is a special server that will be used to warm the lambda function. Besides the common options, you can use the following options:
 
       ### [`invokeFunction`](overrides/invoke_function)
@@ -219,17 +226,22 @@ import { Tabs } from 'nextra/components'
       If you override this, you'll need to handle the warmer event in the wrapper
 
       Possible values are: `aws-lambda`, `dummy` or a `LazyLoadedOverride` that will return the invoke function.
-    </Tabs.Tab>
-    <Tabs.Tab>
-    Initialization function is a special server that will run at build time to initialize the cache. By default, it only initializes the tag cache. Besides the common options, you can use the following options:
 
-    ### `tagCache`
+  </Tabs.Tab>
+
+  <Tabs.Tab>
 
-    Add possibility to override the default tag cache used for the initialization function.
+      Initialization function is a special server that will run at build time to initialize the cache. By default, it only initializes the tag cache. Besides the common options, you can use the following options:
+
+      ### `tagCache`
+
+      Add possibility to override the default tag cache used for the initialization function.
+
+      Possible values are: `dynamodb`, `dynamodb-lite`, `fs-dev`, `dummy` or a `LazyLoadedOverride` that will return the tag cache.
 
-    Possible values are: `dynamodb`, `dynamodb-lite`, `fs-dev`, `dummy` or a `LazyLoadedOverride` that will return the tag cache.
   </Tabs.Tab>
-  </Tabs>
+
+</Tabs>
 
 </Tabs.Tab>
 <Tabs.Tab>
@@ -243,7 +255,7 @@ If you want to specify a different command, you can do so here.
 
 ### `appPath`
 
-The path to the root of the Next.js app's source code. This path is relative from the current process.cwd(). *
+The path to the root of the Next.js app's source code. This path is relative from the current process.cwd().
 
 By default, it is set to `.`
 
@@ -305,5 +317,6 @@ headersAndCookiesPriority: (event) => {
   return 'handler';
 },
 ```
+
 </Tabs.Tab>
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/pages/aws/config/simple_example.mdx b/pages/aws/config/simple_example.mdx
index 77d3b0c..bf981b8 100644
--- a/pages/aws/config/simple_example.mdx
+++ b/pages/aws/config/simple_example.mdx
@@ -1,20 +1,21 @@
-import { Callout } from 'nextra/components';
+import { Callout } from "nextra/components";
 
 Here you can find the most common `open-next.config.ts` file examples that you could easily take as a starting point for your own configuration.
 
 ## Streaming with lambda
 
 <Callout type="info" emoji="ℹ️">
-  If you have an issue with streaming send a message on [discord](https://discord.com/channels/1283128968140161065/1286094576788177059)
-  and contact AWS support to let them know of the issue.
+  If you have an issue with streaming send a message on
+  [discord](https://discord.com/channels/1283128968140161065/1286094576788177059) and contact AWS support to
+  let them know of the issue.
 </Callout>
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {
     override: {
-      wrapper: 'aws-lambda-streaming', // This is necessary to enable lambda streaming
+      wrapper: "aws-lambda-streaming", // This is necessary to enable lambda streaming
     },
   },
 } satisfies OpenNextConfig;
@@ -29,7 +30,7 @@ Be aware that there has been some issues in the past with AWS breaking streaming
 ## Splitting the server
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   // This is the default server, similar to the server-function in open-next v2
   // In this case we are not providing any override, so it will generate a normal lambda (i.e. no streaming)
@@ -38,12 +39,12 @@ const config = {
   functions: {
     myFn: {
       // Patterns needs to use the glob pattern
-      patterns: ['route1', 'route2', 'route3'],
+      patterns: ["route1", "route2", "route3"],
       // For app dir, you need to include route|page, no need to include layout or loading
       // It needs to be prepended with app/ or pages/ depending on the directory used
-      routes: ['app/route1/page', 'app/route2/page', 'pages/route3'],
+      routes: ["app/route1/page", "app/route2/page", "pages/route3"],
       override: {
-        wrapper: 'aws-lambda-streaming',
+        wrapper: "aws-lambda-streaming",
       },
     },
   },
@@ -55,22 +56,20 @@ export default config;
 ## Use aws4fetch instead of AWS sdk
 
 <Callout type="info" emoji="ℹ️">
-  By default we use S3, DynamoDB and SQS for handling ISR/SSG and the fetch
-  cache. We interact with them using AWS sdk v3. This can contribute a lot to
-  the cold start. There is a built-in option to use
-  [aws4fetch](https://github.com/mhart/aws4fetch) instead of the AWS sdk that
-  can reduce cold start up to 300ms. Requires `OpenNext v3.0.3+`. Here is how
-  you enable it:
+  By default we use S3, DynamoDB and SQS for handling ISR/SSG and the fetch cache. We interact with them using
+  AWS sdk v3. This can contribute a lot to the cold start. There is a built-in option to use
+  [aws4fetch](https://github.com/mhart/aws4fetch) instead of the AWS sdk that can reduce cold start up to
+  300ms. Requires `OpenNext v3.0.3+`. Here is how you enable it:
 </Callout>
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {
     override: {
-      tagCache: 'dynamodb-lite',
-      incrementalCache: 's3-lite',
-      queue: 'sqs-lite',
+      tagCache: "dynamodb-lite",
+      incrementalCache: "s3-lite",
+      queue: "sqs-lite",
     },
   },
 } satisfies OpenNextConfig;
@@ -81,12 +80,12 @@ export default config;
 ## Running in Lambda@Edge
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {
-    placement: 'global',
+    placement: "global",
     override: {
-      converter: 'aws-cloudfront',
+      converter: "aws-cloudfront",
     },
   },
 } satisfies OpenNextConfig;
@@ -100,17 +99,18 @@ export default config;
 This is not implemented in SST yet. You'll have to use your own IAC construct to deploy this.
 
 Be aware that this uses the exact same system for ISR/SSG as the default lambda setup. So it will have to have all the proper permissions and env variable to interact with S3, DynamoDB and SQS (Or whatever you override it with). You can see [here](/aws/inner_workings/components/server/node#special-overrides) for more details
+
 </Callout>
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   // In this case, the default server is meant to run as a classic Node server
   // To execute the server you need to run `node index.mjs` inside `.open-next/server-functions/default`
   default: {
     override: {
-      wrapper: 'node',
-      converter: 'node',
+      wrapper: "node",
+      converter: "node",
       // This is necessary to generate a simple dockerfile and for the generated output to know that it needs to deploy on docker
       // You can also provide a string here (i.e. the content of your Dockerfile) which will be used to create the dockerfile
       // You don't have to provide this if you plan on not using docker, or if you plan on using your own custom dockerfile
@@ -122,8 +122,8 @@ const config = {
     // In this case both the api route is in lambda and the rest is in node
     myFn: {
       // Patterns needs to use the glob pattern
-      patterns: ['api/*'],
-      routes: ['app/api/test/route', 'app/api/test2/route'],
+      patterns: ["api/*"],
+      routes: ["app/api/test/route", "app/api/test2/route"],
     },
   },
 } satisfies OpenNextConfig;
@@ -138,15 +138,15 @@ This will generate 2 server functions, the default one and the edge one. The edg
 Edge runtime function have less cold start time, but you can only deploy one route per function. They also do not have the middleware bundled in the function, so you need to use external middleware if you need it in front of the edge function.
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {},
   functions: {
     edge: {
-      runtime: 'edge',
+      runtime: "edge",
       //placement: "global", If you want your function to be deployed globally (i.e. lambda@edge) uncomment this line. Otherwise it will be deployed in the region specified in the stack
-      routes: ['app/api/test/route'],
-      patterns: ['api/test'],
+      routes: ["app/api/test/route"],
+      patterns: ["api/test"],
     },
   },
 } satisfies OpenNextConfig;
@@ -161,15 +161,15 @@ With the default middleware configuration, it is bundled for a deployment in lam
 This is how you can do it:
 
 ```ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
   default: {},
   functions: {
     myFn: {
-      patterns: ['route1', 'route2', 'route3'],
-      routes: ['app/route1/page', 'app/route2/page', 'pages/route3'],
+      patterns: ["route1", "route2", "route3"],
+      routes: ["app/route1/page", "app/route2/page", "pages/route3"],
       override: {
-        wrapper: 'aws-lambda-streaming',
+        wrapper: "aws-lambda-streaming",
       },
     },
   },
diff --git a/pages/aws/contribute/_meta.json b/pages/aws/contribute/_meta.json
index 64c1128..b0d5ba3 100644
--- a/pages/aws/contribute/_meta.json
+++ b/pages/aws/contribute/_meta.json
@@ -1,4 +1,4 @@
 {
   "local_run": "Run locally",
   "plugin": "Internal plugin system"
-}
\ No newline at end of file
+}
diff --git a/pages/aws/contribute/local_run.mdx b/pages/aws/contribute/local_run.mdx
index 970a2cf..cd4f581 100644
--- a/pages/aws/contribute/local_run.mdx
+++ b/pages/aws/contribute/local_run.mdx
@@ -1,20 +1,22 @@
-When making some changes to OpenNext, it can be a bit cumbersome to need to deploy every time you want to test changes. If your change is not dependent on the wrapper or the converter, then you can create a custom `open-next.config.ts` file (you can use another name so that it doesn't conflict with your existing `open-next.config.ts`). 
-
+When making some changes to OpenNext, it can be a bit cumbersome to need to deploy every time you want to test changes. If your change is not dependent on the wrapper or the converter, then you can create a custom `open-next.config.ts` file (you can use another name so that it doesn't conflict with your existing `open-next.config.ts`).
 
 To run `OpenNext` locally:
+
 ```bash
 # This is to build (the config-path is needed if you use a different name than the default one)
 node /path/to/opennextjs-aws/packages/open-next/dist/index.js build --config-path open-next.local.config.ts
 # Then to run the server
 node .open-next/server-functions/default/index.mjs
 ```
+
 ### open-next.local.config.ts
+
 ```typescript
 // open-next.local.config.ts -
 // A good practice would be to use a different name so that it doesn't conflict
 // with your existing open-next.config.ts i.e. open-next.local.config.ts
 // You could also customize it by using custom overrides if you need to.
-import type {OpenNextConfig} from "@opennextjs/aws/types/open-next.js"
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 
 export default {
   default: {
@@ -23,26 +25,26 @@ export default {
       converter: "node",
       incrementalCache: "fs-dev",
       queue: "direct",
-      tagCache: "fs-dev"
-    }
+      tagCache: "fs-dev",
+    },
   },
 
   imageOptimization: {
     override: {
       wrapper: "dummy",
-      converter: "dummy"
+      converter: "dummy",
     },
     loader: "fs-dev",
     // This part is not needed on arm linux, and image optimization will only work in linux
     install: {
       arch: "x64",
-      packages: ["sharp"]
-    }
+      packages: ["sharp"],
+    },
   },
 
   // You can override the build command here so that you don't have to rebuild next every time you make a change
   //buildCommand: "echo 'No build command'",
-} satisfies OpenNextConfig
+} satisfies OpenNextConfig;
 
-export default config
+export default config;
 ```
diff --git a/pages/aws/contribute/plugin.mdx b/pages/aws/contribute/plugin.mdx
index a2041f3..2ecd0c2 100644
--- a/pages/aws/contribute/plugin.mdx
+++ b/pages/aws/contribute/plugin.mdx
@@ -2,7 +2,7 @@ OpenNext use 3 different esbuild plugins internally to recompile or modify the s
 
 #### OpenNext Replacement Plugin
 
-This plugin is used to replace some code in the source code with some other code. 
+This plugin is used to replace some code in the source code with some other code.
 
 Here is a very simple example of how to use it:
 
@@ -15,24 +15,24 @@ openNextPlugin({
     // This is to delete some code from the target file
     deletes: ["id1"],
   })
- 
+
   //To inject arbritary code by using (import at top of file):
- 
+
   //#import
- 
+
   import data from 'data'
   const datum = data.datum
- 
+
   //#endImport
- 
+
   To replace code:
- 
+
   //#override id1
- 
+
   export function overrideMe() {
      // I will replace the "id1" block in the target file
   }
- 
+
   //#endOverride
 ```
 
@@ -47,13 +47,13 @@ openNextResolvePlugin({
   overrides: {
     wrapper: "node",
     converter: "node",
-  }
-})
+  },
+});
 ```
 
 #### OpenNext Edge Plugin
 
-This plugin is used to properly compile routes or middleware built for the `edge` runtime. 
+This plugin is used to properly compile routes or middleware built for the `edge` runtime.
 
 Here is a very simple example of how to use it:
 
@@ -68,4 +68,4 @@ openNextEdgePlugin({
   // If the app should be bundled for cloudflare workers
   isInCloudflare: true
 })
-```
\ No newline at end of file
+```
diff --git a/pages/aws/faq.mdx b/pages/aws/faq.mdx
index 7e9001a..3ad694d 100644
--- a/pages/aws/faq.mdx
+++ b/pages/aws/faq.mdx
@@ -22,4 +22,4 @@ OpenNext is an open source initiative, and there are a couple of advantages when
 
 1. Amplify's Next.js hosting is a black box. Resources are not deployed to your AWS account. All Amplify users share the same CloudFront CDN owned by the Amplify team. This prevents you from customizing the setup, and customization is important if you are looking for Vercel-like features.
 
-1. Amplify's implementation is closed-source. Bug fixes often take much longer to get fixed as you have to go through AWS support. And you are likely to encounter more quirks when hosting Next.js anywhere but Vercel.
\ No newline at end of file
+1. Amplify's implementation is closed-source. Bug fixes often take much longer to get fixed as you have to go through AWS support. And you are likely to encounter more quirks when hosting Next.js anywhere but Vercel.
diff --git a/pages/aws/index.mdx b/pages/aws/index.mdx
index 39d6e43..99ff485 100644
--- a/pages/aws/index.mdx
+++ b/pages/aws/index.mdx
@@ -1,6 +1,6 @@
-import { SITE } from '../../config';
-import { Callout } from 'nextra/components';
-import WindowsSupport from '../../shared/WindowsSupport.mdx';
+import { SITE } from "../../config";
+import { Callout } from "nextra/components";
+import WindowsSupport from "../../shared/WindowsSupport.mdx";
 
 <Callout>
 This docs is for the V3 of OpenNext. If you are looking for the V2 docs, you can find them [here](/aws/v2).
@@ -46,8 +46,8 @@ OpenNext aims to support all Next.js 15 features. Some features are work in prog
 
 ---
 
-<Callout type='info'>
-    <WindowsSupport />
+<Callout type="info">
+  <WindowsSupport />
 </Callout>
 
 ---
diff --git a/pages/aws/inner_workings.mdx b/pages/aws/inner_workings.mdx
index 013fc0f..fb4c724 100644
--- a/pages/aws/inner_workings.mdx
+++ b/pages/aws/inner_workings.mdx
@@ -20,4 +20,4 @@ my-next-app/
     image-optimization-function/   -> Handler code for image optimization backend
     warmer-function/               -> Cron job code to keep server function warm - Not mandatory
     dynamo-provider/               -> Code for a custom resource to populate the Tag Cache - Only necessary for app dir
-```
\ No newline at end of file
+```
diff --git a/pages/aws/inner_workings/architecture.mdx b/pages/aws/inner_workings/architecture.mdx
index 5b8fc3b..f8e09ed 100644
--- a/pages/aws/inner_workings/architecture.mdx
+++ b/pages/aws/inner_workings/architecture.mdx
@@ -14,7 +14,6 @@ We are going to take a look at every component created by OpenNext.
 
 OpenNext will create a `.open-next/assets` folder containing the hashed and un-hashed files. Those files can be directly served without going through the server function. Files in `.open-next/assets` should be served from the root of your website. For example, the file `.open-next/assets/favicon.ico` should be served from `/favicon.ico`.
 
-
 There are two types of files in the `.open-next/assets` folder:
 
 **Hashed files**
@@ -109,4 +108,4 @@ Read more on [how warming works](/aws/v2/inner_workings/warming).
 
 #### Tag Provider backend
 
-This is used to populate the revalidation table with tags.
\ No newline at end of file
+This is used to populate the revalidation table with tags.
diff --git a/pages/aws/inner_workings/cache_interception.mdx b/pages/aws/inner_workings/cache_interception.mdx
index d19ec18..7aa0e56 100644
--- a/pages/aws/inner_workings/cache_interception.mdx
+++ b/pages/aws/inner_workings/cache_interception.mdx
@@ -7,6 +7,7 @@ Since OpenNext 3.1, we have added a new feature that we call Cache Interception
 Enabling this alongside external middleware means that the external middleware will need to have all the proper permissions and env variable to interact with S3, DynamoDB and SQS (Or whatever you override it with). You can see [here](/aws/inner_workings/components/server/node#special-overrides) for more details.
 
 This has the following benefits:
+
 - Faster cold start (No need to load the js associated with the page if the page is cached)
 - ISR/SSG route can be served directly from an external middleware
 - If the external middleware is in front of the CDN, the middleware can be used for every route including ISR/SSG
@@ -16,17 +17,15 @@ To enable cache interception, you need to add `enableCacheInterception` option i
 
 ```ts
 // open-next.config.ts
-import type { OpenNextConfig } from '@opennextjs/aws/types/open-next.js';
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
 const config = {
-  default: {
-  },
+  default: {},
   dangerous: {
     enableCacheInterception: true,
   },
 } satisfies OpenNextConfig;
 
 export default config;
-
 ```
 
-1. PPR outside of vercel does not work in the way they demonstrated. The reason is that the cache system is handled by `NextServer` and it has to reach the server **every single time**. PPR pages cannot be served from the CDN when using `next start` or the standalone ouput as of now. In some cases PPR without vercel can be slower than SSR (especially if your cache is not using the default filesystem).
\ No newline at end of file
+1. PPR outside of vercel does not work in the way they demonstrated. The reason is that the cache system is handled by `NextServer` and it has to reach the server **every single time**. PPR pages cannot be served from the CDN when using `next start` or the standalone ouput as of now. In some cases PPR without vercel can be slower than SSR (especially if your cache is not using the default filesystem).
diff --git a/pages/aws/inner_workings/caching.mdx b/pages/aws/inner_workings/caching.mdx
index a062850..71cc0b6 100644
--- a/pages/aws/inner_workings/caching.mdx
+++ b/pages/aws/inner_workings/caching.mdx
@@ -8,14 +8,13 @@ Also the default Next.js standalone output (or `next start`) does not work in a
 
 Default Next.js also uses the file system to cache files. You can override it by providing your own cache implementation. This is done **automatically** when using OpenNext.
 
-There is also 2 issues with the default `Cache-Control` headers that Next.js sets. 
-They use this header by default `s-maxage=YOUR_REVALIDATION_TIME, stale-while-revalidate`. There is 2 issue with that: 
+There is also 2 issues with the default `Cache-Control` headers that Next.js sets.
+They use this header by default `s-maxage=YOUR_REVALIDATION_TIME, stale-while-revalidate`. There is 2 issue with that:
+
 - `stale-while-revalidate` is not the proper syntax for the `Cache-Control` header. It should be `stale-while-revalidate=TIME_WHERE_YOU_SERVE_STALE`. They added this [undocumented options](https://github.com/vercel/next.js/blob/952da876f7bb8590d0222b2579117f8a2bd301bb/packages/next/src/server/config-shared.ts#L202) to remedy this in recent version of Next
 - Setting `s-maxage` to the same value for every request to the same page could be a bad idea.
-Next can serve different content based on if you request the full html or are doing client side navigation (RSC or JSON for page router)
-  
+  Next can serve different content based on if you request the full html or are doing client side navigation (RSC or JSON for page router)
   This can cause inconsistencies in the cache with ISR especially when you can have big revalidation time.
-  
   For example, let's assume you use app router, you have a link to your homepage in your main navbar and you set ISR to 1 day. Every other page will have a different RSC cache entry (for client side navigation). This will result in as many cache entry as you have pages in your app which all will have that same 1 day `s-maxage` value but could have been requested at very different time. This could lead to some pages being served with stale content for as long as 2 day.
 
 **All of these issues are automatically fixed for you in OpenNext**
@@ -58,7 +57,7 @@ async function invalidateCloudFrontPaths(paths: string[]) {
           Items: paths,
         },
       },
-    }),
+    })
   );
 }
 ```
@@ -80,7 +79,7 @@ await invalidateCloudFrontPaths(["/page/*"]);
 For on-demand revalidation via the [`next/cache` module](https://nextjs.org/docs/app/building-your-application/data-fetching/revalidating#using-on-demand-revalidation), if you want to retrieve the associated paths for a given tag, you can use this function:
 
 ```ts
-import { DynamoDBClient, QueryCommand } from '@aws-sdk/client-dynamodb';
+import { DynamoDBClient, QueryCommand } from "@aws-sdk/client-dynamodb";
 
 const client = new DynamoDBClient({ region: process.env.CACHE_BUCKET_REGION });
 
@@ -96,14 +95,9 @@ async function getPaths(tag: string) {
         ExpressionAttributeValues: {
           ":tag": { S: `${process.env.NEXT_BUILD_ID}/${tag}` },
         },
-      }),
-    );
-    return (
-      Items?.map(
-        (item) =>
-          item.path?.S?.replace(`${process.env.NEXT_BUILD_ID}/`, "") ?? "",
-      ) ?? []
+      })
     );
+    return Items?.map((item) => item.path?.S?.replace(`${process.env.NEXT_BUILD_ID}/`, "") ?? "") ?? [];
   } catch (e) {
     console.error("Failed to get by tag", e);
     return [];
diff --git a/pages/aws/inner_workings/components/_meta.json b/pages/aws/inner_workings/components/_meta.json
index 5291967..18c948c 100644
--- a/pages/aws/inner_workings/components/_meta.json
+++ b/pages/aws/inner_workings/components/_meta.json
@@ -6,4 +6,4 @@
   "revalidation": "Revalidation",
   "warmer": "Warmer",
   "initializer": "Initializer"
-}
\ No newline at end of file
+}
diff --git a/pages/aws/inner_workings/components/image_optimization.mdx b/pages/aws/inner_workings/components/image_optimization.mdx
index 6bef28b..b80f59a 100644
--- a/pages/aws/inner_workings/components/image_optimization.mdx
+++ b/pages/aws/inner_workings/components/image_optimization.mdx
@@ -1,20 +1,23 @@
-The image optimization backend is used to transform images to the desired format and quality. 
+The image optimization backend is used to transform images to the desired format and quality.
 It should be accessible at `/_next/image?url=URL_OF_THE_IMAGE&q=QUALITY&w=WIDTH` and should be used as a proxy to the image source.
 
 Streaming is **useless** for this backend, as we have to wait for the image to be transformed even for the headers. In the future this backend might be enhanced to support streaming.
 
 ### Environment Variables
-  - BUCKET_NAME: The name of the bucket where the images are stored
-  - BUCKET_KEY_PREFIX: The prefix of the key where the images are stored
-  - OPENNEXT_STATIC_ETAG: If set to `true`, the ETag header will be set to the hash of the properties of the image (href, width, quality, buildId). This will allow us to return 304 responses when the image properties has not changed.
+
+- BUCKET_NAME: The name of the bucket where the images are stored
+- BUCKET_KEY_PREFIX: The prefix of the key where the images are stored
+- OPENNEXT_STATIC_ETAG: If set to `true`, the ETag header will be set to the hash of the properties of the image (href, width, quality, buildId). This will allow us to return 304 responses when the image properties has not changed.
 
 ### Special Overrides
 
 #### Loader
+
 It is used to load **internal** images. By default, it uses S3 API to load the images from the bucket.
 
 You can customize the loader by providing a custom loader function to the `loader` prop.
-It should return 
+It should return
+
 ```typescript
 type ImageLoader = BaseOverride & {
   load: (url: string) => Promise<{
@@ -22,5 +25,5 @@ type ImageLoader = BaseOverride & {
     contentType?: string;
     cacheControl?: string;
   }>;
-}
-```
\ No newline at end of file
+};
+```
diff --git a/pages/aws/inner_workings/components/initializer.mdx b/pages/aws/inner_workings/components/initializer.mdx
index ced2cac..11bb84d 100644
--- a/pages/aws/inner_workings/components/initializer.mdx
+++ b/pages/aws/inner_workings/components/initializer.mdx
@@ -1,6 +1,7 @@
 The Initializer is a special backend that should run only once during deployment. It's default role is to populate the tag cache with the prerendered tags.
 
-It uses these events and results: 
+It uses these events and results:
+
 ```typescript
 interface InitializationFunctionEvent {
   type: "initializationFunction";
@@ -13,4 +14,4 @@ type InitializationFunctionResult = InitializationFunctionEvent;
 
 ### Special Overrides
 
-The initializer uses the tag cache to store the prerendered tags. 
\ No newline at end of file
+The initializer uses the tag cache to store the prerendered tags.
diff --git a/pages/aws/inner_workings/components/middleware.mdx b/pages/aws/inner_workings/components/middleware.mdx
index 4694e57..d3327e6 100644
--- a/pages/aws/inner_workings/components/middleware.mdx
+++ b/pages/aws/inner_workings/components/middleware.mdx
@@ -1,20 +1,23 @@
-import { Callout } from 'nextra/components'
+import { Callout } from "nextra/components";
 
 <Callout type="warning" emoji="⚠️">
-  When we talk about middleware in this docs, we are referring both to the next `middleware` as well as the whole `routing` layer of next.
-  For example, `next.config.js` headers, redirects, rewrites, etc. are all considered `routing` in this context.
+  When we talk about middleware in this docs, we are referring both to the next `middleware` as well as the
+  whole `routing` layer of next. For example, `next.config.js` headers, redirects, rewrites, etc. are all
+  considered `routing` in this context.
 </Callout>
 
 Since V3, you can decide to move the middleware outside of the server into it's own function that you can place in front of your others backend functions.
 
 By default, the middleware is inside the server, but you can move it outside by setting `middleware.external` to `true` in your `open-next.config.ts` file.
+
 ```ts
 {
   middleware: {
-    external: true
+    external: true;
   }
 }
 ```
+
 It uses the `aws-lambda` wrapper and the `aws-cloudfront` converter by default so that you can use it with AWS Lambda@edge and Cloudfront.
 You can also use it inside Cloudflare Workers by setting the wrapper to `cloudflare` and the converter to `edge`.
 
@@ -22,9 +25,10 @@ You can also use it inside Cloudflare Workers by setting the wrapper to `cloudfl
 
 #### Origin resolver
 
-Since your app could be split into different origins, you need to be able to retrieve the right origin for the request. That's the purpose of the `originResolver` function. 
+Since your app could be split into different origins, you need to be able to retrieve the right origin for the request. That's the purpose of the `originResolver` function.
 
 By default, it uses the `pattern-env` resolver which uses an `OPEN_NEXT_ORIGIN` environment variable to resolve the origin as well as the pattern defined in your `open-next.config.ts`. This env var should be a stringified version of an object of this shape:
+
 ```ts
 {
   // Key should be the same as the one used in `open-next.config.ts` for the functions
@@ -36,10 +40,12 @@ By default, it uses the `pattern-env` resolver which uses an `OPEN_NEXT_ORIGIN`
   }
 }
 ```
+
 You can of course override this behavior by providing your own `originResolver` function in your `open-next.config.ts` file.
 This is the type of the `originResolver` function:
+
 ```ts
 type OriginResolver = BaseOverride & {
   resolve: (path: string) => Promise<Origin | false>;
 };
-```
\ No newline at end of file
+```
diff --git a/pages/aws/inner_workings/components/overview.mdx b/pages/aws/inner_workings/components/overview.mdx
index aa040fc..481c97a 100644
--- a/pages/aws/inner_workings/components/overview.mdx
+++ b/pages/aws/inner_workings/components/overview.mdx
@@ -1,4 +1,4 @@
-import { Callout } from 'nextra/components';
+import { Callout } from "nextra/components";
 
 <Callout>
   This documentation is still a work in progress. Some parts might be missing or incomplete.
@@ -47,10 +47,7 @@ The wrapper is the main entrypoint for the backend. This is the type of the wrap
 type WrapperHandler<
   E extends BaseEventOrResult = InternalEvent,
   R extends BaseEventOrResult = InternalResult,
-> = (
-  handler: OpenNextHandler<E, R>,
-  converter: Converter<E, R>,
-) => Promise<(...args: any[]) => any>;
+> = (handler: OpenNextHandler<E, R>, converter: Converter<E, R>) => Promise<(...args: any[]) => any>;
 
 export type Wrapper<
   E extends BaseEventOrResult = InternalEvent,
diff --git a/pages/aws/inner_workings/components/revalidation.mdx b/pages/aws/inner_workings/components/revalidation.mdx
index 7bc1253..f2136e3 100644
--- a/pages/aws/inner_workings/components/revalidation.mdx
+++ b/pages/aws/inner_workings/components/revalidation.mdx
@@ -2,6 +2,7 @@ The revalidation backend is used to read the queue and revalidate the routes. It
 For every received message it will trigger a `HEAD` request with `x-prerender-revalidate` header to the host.
 
 ### Special Event and Result types
+
 ```typescript
 interface RevalidateEvent {
   type: "revalidate";
@@ -10,7 +11,7 @@ interface RevalidateEvent {
     url: string;
   }[];
 }
- interface RevalidateResult {
+interface RevalidateResult {
   type: "revalidate";
- }
-```
\ No newline at end of file
+}
+```
diff --git a/pages/aws/inner_workings/components/server/edge.mdx b/pages/aws/inner_workings/components/server/edge.mdx
index 30404ce..1333ed7 100644
--- a/pages/aws/inner_workings/components/server/edge.mdx
+++ b/pages/aws/inner_workings/components/server/edge.mdx
@@ -1 +1 @@
-TODO
\ No newline at end of file
+TODO
diff --git a/pages/aws/inner_workings/components/server/node.mdx b/pages/aws/inner_workings/components/server/node.mdx
index 4185b6f..9d377d4 100644
--- a/pages/aws/inner_workings/components/server/node.mdx
+++ b/pages/aws/inner_workings/components/server/node.mdx
@@ -26,7 +26,7 @@ To facilitate this:
 #### Lifetime of an SSG request for a page revalidated using `revalidateTag`
 
 1. You revalidate the page using `revalidateTag` or `revalidatePath`. You should also invalidate the cache in Cloudfront
-2. Cloudfront receives a request for a page. 
+2. Cloudfront receives a request for a page.
 3. Cloudfront forwards the request to the `server-function`.
 4. The `server-function` checks in the incremental cache, then in the tag cache. If the page is stale in the tag cache, it will trigger an immediate revalidation and send the updated response back to Cloudfront.
 5. The user will receive the updated version of the page with the `x-next-cache` header set to `MISS`.
@@ -48,12 +48,14 @@ You can look at the expected types [here](https://github.com/sst/open-next/blob/
 The default S3 Incremental Cache uses the `@aws-sdk/client-s3` to interact with the S3 bucket. It needs to have the proper permissions to read and write to the bucket.
 
 File in S3 should follow the following structure:
+
 - `Key_Prefix/BUILD_ID/path/to/page.cache` - For the cache of a page
 - `Key_Prefix/__fetch/BUILD_ID/fetch-cache-key` - For the fetch cache
 
 The default S3 Incremental Cache can be configured using the following environment variables:
 
 ###### Environment Variables
+
 - CACHE_BUCKET_REGION: The region of the S3 bucket
 - CACHE_BUCKET_NAME: The name of the S3 bucket
 - CACHE_BUCKET_KEY_PREFIX: The prefix of the keys in the S3 bucket - Optional
@@ -72,20 +74,22 @@ You can look at the expected types [here](https://github.com/sst/open-next/blob/
 The default DynamoDB Tag Cache uses the `@aws-sdk/client-dynamodb` to interact with the DynamoDB table. It needs to have the proper permissions to read and write to the table.
 
 Tags in DynamoDB should follow the following structure:
-```typescript 
-type Tag = {
-  path: string, // The path of the page
-  tag: string, // The tag of the page
-  revalidatedAt: number, // The time at which the page has been revalidated
-}
 
+```typescript
+type Tag = {
+  path: string; // The path of the page
+  tag: string; // The tag of the page
+  revalidatedAt: number; // The time at which the page has been revalidated
+};
 ```
+
 We use an index called `revalidate` with `path` as a partition key and `revalidatedAt` as the sort key.
 It needs to be pre-populated with the tags of the pages that are being generated.
 
 The default DynamoDB Tag Cache can be configured using the following environment variables:
 
 ###### Environment Variables
+
 - CACHE_BUCKET_REGION: The region of the DynamoDB table
 - CACHE_DYNAMO_TABLE: The name of the DynamoDB table
 - AWS_SDK_DYNAMODB_MAX_ATTEMPTS: The maximum number of attempts to make to the DynamoDB table - Optional
@@ -99,6 +103,7 @@ By default, OpenNext uses SQS as the default revalidation queue.
 You can override the default queue by setting the `override.queue` property in the `open-next.config.ts` file.
 
 Here is the expected type for the queue override:
+
 ```ts
 interface QueueMessage {
   MessageDeduplicationId: string;
@@ -114,6 +119,7 @@ export interface Queue {
   name: string;
 }
 ```
+
 The send function will be called when a page is marked as `STALE`. You don't have to use a queue here, you can use any other mechanism to send the message to the revalidation worker or even do the revalidation in the same process.
 
 #### Shared Environment Variables
@@ -129,4 +135,4 @@ The default SQS Revalidation Queue can be configured using the following environ
 ###### Environment Variables
 
 - REVALIDATION_QUEUE_REGION: The region of the SQS queue
-- REVALIDATION_QUEUE_URL: The URL of the SQS queue
\ No newline at end of file
+- REVALIDATION_QUEUE_URL: The URL of the SQS queue
diff --git a/pages/aws/inner_workings/components/warmer.mdx b/pages/aws/inner_workings/components/warmer.mdx
index 65ae199..960e46b 100644
--- a/pages/aws/inner_workings/components/warmer.mdx
+++ b/pages/aws/inner_workings/components/warmer.mdx
@@ -1,6 +1,7 @@
 The warmer backend is used to warm up the server lambda in case of serverless. This is useful to avoid cold starts.
 
 ### Special Event and Result
+
 ```typescript
 interface WarmerEvent {
   type: "warmer";
@@ -19,10 +20,12 @@ interface WarmerResponse {
 ### Special Overrides
 
 #### Invoke function
-You can customize the `invoke` function to handle the `warmer` event. By default it uses lambda invoke command. The default invoke needs a `WARM_PARAMS` environment variable that is a stringified version of this 
+
+You can customize the `invoke` function to handle the `warmer` event. By default it uses lambda invoke command. The default invoke needs a `WARM_PARAMS` environment variable that is a stringified version of this
+
 ```typescript
 {
   concurrency: number;
   function: string;
 }[]
-```
\ No newline at end of file
+```
diff --git a/pages/aws/inner_workings/routing.mdx b/pages/aws/inner_workings/routing.mdx
index 93b0785..11e762a 100644
--- a/pages/aws/inner_workings/routing.mdx
+++ b/pages/aws/inner_workings/routing.mdx
@@ -1,4 +1,4 @@
-OpenNext doesn't use the default routing provided by Next.js. Instead, it uses its own routing system. 
+OpenNext doesn't use the default routing provided by Next.js. Instead, it uses its own routing system.
 
 Historically, OpenNext used the same routing system as Next.js. But in Next 13.4.13, they moved the routing system outside of `NextServer` and separated every major part of the app (i.e. app router, page router and the routing) inside jest workers. This caused terrible cold start (around 8s for a default `create next-app` app) and made it impossible to serve ISR/SSG pages inside lambda. Since then, OpenNext has been using its own routing system for every app that uses Next 13.4.13 or higher. FYI Vercel use an undocumented `minimalMode` inside `NextServer` to bypass the routing and cache system so that it is done in their infra instead of the lambda.
 
@@ -6,7 +6,7 @@ This move also allow OpenNext to have a more flexible routing system. With OpenN
 
 Here is a list of features that OpenNext routing system handle:
 
-- From `next.config.js` (the rest is handled by `NextServer` itself): 
+- From `next.config.js` (the rest is handled by `NextServer` itself):
   - Headers
   - Redirects
   - Rewrites
@@ -16,7 +16,6 @@ Here is a list of features that OpenNext routing system handle:
 - [Optional Cache Interception](/aws/inner_workings/cache_interception) (i.e. serve ISR/SSG directly from the routing layer)
 - Handle 404 in some cases (i.e. when the page does not correspond to any of the regex routes)
 
-
 #### Next Middleware
 
-The Next middleware in OpenNext is not running in the same way as in Next.js. In Next.js, the middleware is running inside the `NextServer` inside a fake edge runtime. In OpenNext, we modify the middleware and run it fully inside the routing layer. So if you run the routing layer in Node, you can use Node api inside the middleware (it's a bit tricky because it won't work with `next dev` and involves some workaround because Next will remove Node api during bundling. Some example [here](/aws/config/custom_overrides#define-a-global-to-use-node-in-the-middleware)).
\ No newline at end of file
+The Next middleware in OpenNext is not running in the same way as in Next.js. In Next.js, the middleware is running inside the `NextServer` inside a fake edge runtime. In OpenNext, we modify the middleware and run it fully inside the routing layer. So if you run the routing layer in Node, you can use Node api inside the middleware (it's a bit tricky because it won't work with `next dev` and involves some workaround because Next will remove Node api during bundling. Some example [here](/aws/config/custom_overrides#define-a-global-to-use-node-in-the-middleware)).
diff --git a/pages/aws/migration.mdx b/pages/aws/migration.mdx
index d4ea3ef..4d3d90c 100644
--- a/pages/aws/migration.mdx
+++ b/pages/aws/migration.mdx
@@ -35,7 +35,7 @@ You should remove some stuff from your `next.config.js` file, otherwise you'll g
 ```js
 module.exports = {
   // ...
-  target: 'serverless', // remove this
+  target: "serverless", // remove this
   // ...
-}
+};
 ```
diff --git a/pages/aws/reference-implementation.mdx b/pages/aws/reference-implementation.mdx
index d2898cc..13227fd 100644
--- a/pages/aws/reference-implementation.mdx
+++ b/pages/aws/reference-implementation.mdx
@@ -1,4 +1,4 @@
-import { Callout } from 'nextra/components'
+import { Callout } from "nextra/components";
 
 In order to help deploying OpenNext with your own IAC implementation, we created a simple reference implementation using aws-cdk.
 
@@ -6,11 +6,12 @@ If you wish to use it, just copy the code for the construct below. If you use it
 
 <Callout type="warning" emoji="⚠️">
 
-  This is a reference implementation, and it is not meant to be used in production as is.
+This is a reference implementation, and it is not meant to be used in production as is.
 
-	This is just here to help you understand how to use the new features of OpenNext.
+    This is just here to help you understand how to use the new features of OpenNext.
+
+There is some features that are not implemented like the warmer function, or everything related to lambda@edge(It requires inserting env variables which is out of scope of this implementation).
 
-  There is some features that are not implemented like the warmer function, or everything related to lambda@edge(It requires inserting env variables which is out of scope of this implementation).
 </Callout>
 
 ```ts
@@ -19,49 +20,33 @@ import { readFileSync } from "fs";
 import path from "path";
 import { BlockPublicAccess, Bucket } from "aws-cdk-lib/aws-s3";
 import { BucketDeployment, Source } from "aws-cdk-lib/aws-s3-deployment";
+import { CustomResource, Duration, Fn, RemovalPolicy, Stack } from "aws-cdk-lib/core";
 import {
-	CustomResource,
-	Duration,
-	Fn,
-	RemovalPolicy,
-	Stack,
-} from "aws-cdk-lib/core";
-import {
-	AllowedMethods,
-	BehaviorOptions,
-	CacheCookieBehavior,
-	CacheHeaderBehavior,
-	CachePolicy,
-	CacheQueryStringBehavior,
-	CachedMethods,
-	Distribution,
-	ICachePolicy,
-	ViewerProtocolPolicy,
-	FunctionEventType,
-	OriginRequestPolicy,
-	Function as CloudfrontFunction,
-	FunctionCode,
+  AllowedMethods,
+  BehaviorOptions,
+  CacheCookieBehavior,
+  CacheHeaderBehavior,
+  CachePolicy,
+  CacheQueryStringBehavior,
+  CachedMethods,
+  Distribution,
+  ICachePolicy,
+  ViewerProtocolPolicy,
+  FunctionEventType,
+  OriginRequestPolicy,
+  Function as CloudfrontFunction,
+  FunctionCode,
 } from "aws-cdk-lib/aws-cloudfront";
 import { HttpOrigin, S3Origin } from "aws-cdk-lib/aws-cloudfront-origins";
 import {
-	Code,
-	Function as CdkFunction,
-	FunctionUrlAuthType,
-	InvokeMode,
-	Runtime,
+  Code,
+  Function as CdkFunction,
+  FunctionUrlAuthType,
+  InvokeMode,
+  Runtime,
 } from "aws-cdk-lib/aws-lambda";
-import {
-	TableV2 as Table,
-	AttributeType,
-	Billing,
-} from "aws-cdk-lib/aws-dynamodb";
-import {
-	Service,
-	Source as AppRunnerSource,
-	Memory,
-	HealthCheck,
-	Cpu,
-} from "@aws-cdk/aws-apprunner-alpha";
+import { TableV2 as Table, AttributeType, Billing } from "aws-cdk-lib/aws-dynamodb";
+import { Service, Source as AppRunnerSource, Memory, HealthCheck, Cpu } from "@aws-cdk/aws-apprunner-alpha";
 import { DockerImageAsset } from "aws-cdk-lib/aws-ecr-assets";
 import { Queue } from "aws-cdk-lib/aws-sqs";
 import { SqsEventSource } from "aws-cdk-lib/aws-lambda-event-sources";
@@ -70,365 +55,340 @@ import { Provider } from "aws-cdk-lib/custom-resources";
 import { RetentionDays } from "aws-cdk-lib/aws-logs";
 
 type BaseFunction = {
-	handler: string;
-	bundle: string;
+  handler: string;
+  bundle: string;
 };
 
 type OpenNextFunctionOrigin = {
-	type: "function";
-	streaming?: boolean;
+  type: "function";
+  streaming?: boolean;
 } & BaseFunction;
 
 type OpenNextECSOrigin = {
-	type: "ecs";
-	bundle: string;
-	dockerfile: string;
+  type: "ecs";
+  bundle: string;
+  dockerfile: string;
 };
 
 type OpenNextS3Origin = {
-	type: "s3";
-	originPath: string;
-	copy: {
-		from: string;
-		to: string;
-		cached: boolean;
-		versionedSubDir?: string;
-	}[];
+  type: "s3";
+  originPath: string;
+  copy: {
+    from: string;
+    to: string;
+    cached: boolean;
+    versionedSubDir?: string;
+  }[];
 };
 
-type OpenNextOrigins =
-	| OpenNextFunctionOrigin
-	| OpenNextECSOrigin
-	| OpenNextS3Origin;
+type OpenNextOrigins = OpenNextFunctionOrigin | OpenNextECSOrigin | OpenNextS3Origin;
 
 interface OpenNextOutput {
-	edgeFunctions: {
-		[key: string]: BaseFunction;
-	};
-	origins: {
-		s3: OpenNextS3Origin;
-		default: OpenNextFunctionOrigin | OpenNextECSOrigin;
-		imageOptimizer: OpenNextFunctionOrigin | OpenNextECSOrigin;
-		[key: string]: OpenNextOrigins;
-	};
-	behaviors: {
-		pattern: string;
-		origin?: string;
-		edgeFunction?: string;
-	}[];
-	additionalProps?: {
-		disableIncrementalCache?: boolean;
-		disableTagCache?: boolean;
-		initializationFunction?: BaseFunction;
-		warmer?: BaseFunction;
-		revalidationFunction?: BaseFunction;
-	};
+  edgeFunctions: {
+    [key: string]: BaseFunction;
+  };
+  origins: {
+    s3: OpenNextS3Origin;
+    default: OpenNextFunctionOrigin | OpenNextECSOrigin;
+    imageOptimizer: OpenNextFunctionOrigin | OpenNextECSOrigin;
+    [key: string]: OpenNextOrigins;
+  };
+  behaviors: {
+    pattern: string;
+    origin?: string;
+    edgeFunction?: string;
+  }[];
+  additionalProps?: {
+    disableIncrementalCache?: boolean;
+    disableTagCache?: boolean;
+    initializationFunction?: BaseFunction;
+    warmer?: BaseFunction;
+    revalidationFunction?: BaseFunction;
+  };
 }
 
 interface OpenNextCdkReferenceImplementationProps {
-	openNextPath: string;
+  openNextPath: string;
 }
 
 export class OpenNextCdkReferenceImplementation extends Construct {
-	private openNextOutput: OpenNextOutput;
-	private bucket: Bucket;
-	private table: Table;
-	private queue: Queue;
-
-	private staticCachePolicy: ICachePolicy;
-	private serverCachePolicy: CachePolicy;
-
-	public distribution: Distribution;
-
-	constructor(
-		scope: Construct,
-		id: string,
-		props: OpenNextCdkReferenceImplementationProps,
-	) {
-		super(scope, id);
-		this.openNextOutput = JSON.parse(
-			readFileSync(
-				path.join(props.openNextPath, "open-next.output.json"),
-				"utf-8",
-			),
-		) as OpenNextOutput;
-
-		this.bucket = new Bucket(this, "OpenNextBucket", {
-			publicReadAccess: false,
-			blockPublicAccess: BlockPublicAccess.BLOCK_ALL,
-			autoDeleteObjects: true,
-			removalPolicy: RemovalPolicy.DESTROY,
-			enforceSSL: true,
-		});
-		this.table = this.createRevalidationTable();
-		this.queue = this.createRevalidationQueue();
-
-		const origins = this.createOrigins();
-		this.serverCachePolicy = this.createServerCachePolicy();
-		this.staticCachePolicy = this.createStaticCachePolicy();
-		this.distribution = this.createDistribution(origins);
-	}
-
-	private createRevalidationTable() {
-		const table = new Table(this, "RevalidationTable", {
-			partitionKey: { name: "tag", type: AttributeType.STRING },
-			sortKey: { name: "path", type: AttributeType.STRING },
-			pointInTimeRecovery: true,
-			billing: Billing.onDemand(),
-			globalSecondaryIndexes: [
-				{
-					indexName: "revalidate",
-					partitionKey: { name: "path", type: AttributeType.STRING },
-					sortKey: { name: "revalidatedAt", type: AttributeType.NUMBER },
-				},
-			],
-			removalPolicy: RemovalPolicy.DESTROY,
-		});
-
-		const initFn = this.openNextOutput.additionalProps?.initializationFunction;
-
-		const insertFn = new CdkFunction(this, "RevalidationInsertFunction", {
-			description: "Next.js revalidation data insert",
-			handler: initFn?.handler ?? "index.handler",
-			// code: Code.fromAsset(initFn?.bundle ?? ""),
-			code: Code.fromAsset(".open-next/dynamodb-provider"),
-			runtime: Runtime.NODEJS_18_X,
-			timeout: Duration.minutes(15),
-			memorySize: 128,
-			environment: {
-				CACHE_DYNAMO_TABLE: table.tableName,
-			},
-		});
-
-		const provider = new Provider(this, "RevalidationProvider", {
-			onEventHandler: insertFn,
-			logRetention: RetentionDays.ONE_DAY,
-		});
-
-		new CustomResource(this, "RevalidationResource", {
-			serviceToken: provider.serviceToken,
-			properties: {
-				version: Date.now().toString(),
-			},
-		});
-
-		return table;
-	}
-
-	private createOrigins() {
-		const {
-			s3: s3Origin,
-			default: defaultOrigin,
-			imageOptimizer: imageOrigin,
-			...restOrigins
-		} = this.openNextOutput.origins;
-		const s3 = new S3Origin(this.bucket, {
-			originPath: s3Origin.originPath,
-		});
-		for (const copy of s3Origin.copy) {
-			new BucketDeployment(this, `OpenNextBucketDeployment${copy.from}`, {
-				sources: [Source.asset(copy.from)],
-				destinationBucket: this.bucket,
-				destinationKeyPrefix: copy.to,
-				prune: false,
-			});
-		}
-		const origins = {
-			s3: new S3Origin(this.bucket, {
-				originPath: s3Origin.originPath,
-				originAccessIdentity: undefined,
-			}),
-			default:
-				defaultOrigin.type === "function"
-					? this.createFunctionOrigin("default", defaultOrigin)
-					: this.createAppRunnerOrigin("default", defaultOrigin),
-			imageOptimizer:
-				imageOrigin.type === "function"
-					? this.createFunctionOrigin("imageOptimizer", imageOrigin)
-					: this.createAppRunnerOrigin("imageOptimizer", imageOrigin),
-			...Object.entries(restOrigins).reduce(
-				(acc, [key, value]) => {
-					if (value.type === "function") {
-						acc[key] = this.createFunctionOrigin(key, value);
-					} else if (value.type === "ecs") {
-						acc[key] = this.createAppRunnerOrigin(key, value);
-					}
-					return acc;
-				},
-				{} as Record<string, HttpOrigin>,
-			),
-		};
-		return origins;
-	}
-
-	private createRevalidationQueue() {
-		const queue = new Queue(this, "RevalidationQueue", {
-			fifo: true,
-			receiveMessageWaitTime: Duration.seconds(20),
-		});
-		const consumer = new CdkFunction(this, "RevalidationFunction", {
-			description: "Next.js revalidator",
-			handler: "index.handler",
-			code: Code.fromAsset(
-				this.openNextOutput.additionalProps?.revalidationFunction?.bundle ?? "",
-			),
-			runtime: Runtime.NODEJS_18_X,
-			timeout: Duration.seconds(30),
-		});
-		consumer.addEventSource(new SqsEventSource(queue, { batchSize: 5 }));
-		return queue;
-	}
-
-	private getEnvironment() {
-		return {
-			CACHE_BUCKET_NAME: this.bucket.bucketName,
-			CACHE_BUCKET_KEY_PREFIX: "_cache",
-			CACHE_BUCKET_REGION: Stack.of(this).region,
-			REVALIDATION_QUEUE_URL: this.queue.queueUrl,
-			REVALIDATION_QUEUE_REGION: Stack.of(this).region,
-			CACHE_DYNAMO_TABLE: this.table.tableName,
-			// Those 2 are used only for image optimizer
-			BUCKET_NAME: this.bucket.bucketName,
-			BUCKET_KEY_PREFIX: "_assets",
-		};
-	}
-
-	private grantPermissions(grantable: IGrantable) {
-		this.bucket.grantReadWrite(grantable);
-		this.table.grantReadWriteData(grantable);
-		this.queue.grantSendMessages(grantable);
-	}
-
-	private createFunctionOrigin(key: string, origin: OpenNextFunctionOrigin) {
-		const environment = this.getEnvironment();
-		const fn = new CdkFunction(this, `${key}Function`, {
-			runtime: Runtime.NODEJS_18_X,
-			handler: origin.handler,
-			code: Code.fromAsset(origin.bundle),
-			environment,
-			memorySize: 1024,
-		});
-		const fnUrl = fn.addFunctionUrl({
-			authType: FunctionUrlAuthType.NONE,
-			invokeMode: origin.streaming
-				? InvokeMode.RESPONSE_STREAM
-				: InvokeMode.BUFFERED,
-		});
-		this.grantPermissions(fn);
-		return new HttpOrigin(Fn.parseDomainName(fnUrl.url));
-	}
+  private openNextOutput: OpenNextOutput;
+  private bucket: Bucket;
+  private table: Table;
+  private queue: Queue;
+
+  private staticCachePolicy: ICachePolicy;
+  private serverCachePolicy: CachePolicy;
+
+  public distribution: Distribution;
+
+  constructor(scope: Construct, id: string, props: OpenNextCdkReferenceImplementationProps) {
+    super(scope, id);
+    this.openNextOutput = JSON.parse(
+      readFileSync(path.join(props.openNextPath, "open-next.output.json"), "utf-8")
+    ) as OpenNextOutput;
+
+    this.bucket = new Bucket(this, "OpenNextBucket", {
+      publicReadAccess: false,
+      blockPublicAccess: BlockPublicAccess.BLOCK_ALL,
+      autoDeleteObjects: true,
+      removalPolicy: RemovalPolicy.DESTROY,
+      enforceSSL: true,
+    });
+    this.table = this.createRevalidationTable();
+    this.queue = this.createRevalidationQueue();
+
+    const origins = this.createOrigins();
+    this.serverCachePolicy = this.createServerCachePolicy();
+    this.staticCachePolicy = this.createStaticCachePolicy();
+    this.distribution = this.createDistribution(origins);
+  }
+
+  private createRevalidationTable() {
+    const table = new Table(this, "RevalidationTable", {
+      partitionKey: { name: "tag", type: AttributeType.STRING },
+      sortKey: { name: "path", type: AttributeType.STRING },
+      pointInTimeRecovery: true,
+      billing: Billing.onDemand(),
+      globalSecondaryIndexes: [
+        {
+          indexName: "revalidate",
+          partitionKey: { name: "path", type: AttributeType.STRING },
+          sortKey: { name: "revalidatedAt", type: AttributeType.NUMBER },
+        },
+      ],
+      removalPolicy: RemovalPolicy.DESTROY,
+    });
+
+    const initFn = this.openNextOutput.additionalProps?.initializationFunction;
+
+    const insertFn = new CdkFunction(this, "RevalidationInsertFunction", {
+      description: "Next.js revalidation data insert",
+      handler: initFn?.handler ?? "index.handler",
+      // code: Code.fromAsset(initFn?.bundle ?? ""),
+      code: Code.fromAsset(".open-next/dynamodb-provider"),
+      runtime: Runtime.NODEJS_18_X,
+      timeout: Duration.minutes(15),
+      memorySize: 128,
+      environment: {
+        CACHE_DYNAMO_TABLE: table.tableName,
+      },
+    });
+
+    const provider = new Provider(this, "RevalidationProvider", {
+      onEventHandler: insertFn,
+      logRetention: RetentionDays.ONE_DAY,
+    });
+
+    new CustomResource(this, "RevalidationResource", {
+      serviceToken: provider.serviceToken,
+      properties: {
+        version: Date.now().toString(),
+      },
+    });
+
+    return table;
+  }
+
+  private createOrigins() {
+    const {
+      s3: s3Origin,
+      default: defaultOrigin,
+      imageOptimizer: imageOrigin,
+      ...restOrigins
+    } = this.openNextOutput.origins;
+    const s3 = new S3Origin(this.bucket, {
+      originPath: s3Origin.originPath,
+    });
+    for (const copy of s3Origin.copy) {
+      new BucketDeployment(this, `OpenNextBucketDeployment${copy.from}`, {
+        sources: [Source.asset(copy.from)],
+        destinationBucket: this.bucket,
+        destinationKeyPrefix: copy.to,
+        prune: false,
+      });
+    }
+    const origins = {
+      s3: new S3Origin(this.bucket, {
+        originPath: s3Origin.originPath,
+        originAccessIdentity: undefined,
+      }),
+      default:
+        defaultOrigin.type === "function"
+          ? this.createFunctionOrigin("default", defaultOrigin)
+          : this.createAppRunnerOrigin("default", defaultOrigin),
+      imageOptimizer:
+        imageOrigin.type === "function"
+          ? this.createFunctionOrigin("imageOptimizer", imageOrigin)
+          : this.createAppRunnerOrigin("imageOptimizer", imageOrigin),
+      ...Object.entries(restOrigins).reduce(
+        (acc, [key, value]) => {
+          if (value.type === "function") {
+            acc[key] = this.createFunctionOrigin(key, value);
+          } else if (value.type === "ecs") {
+            acc[key] = this.createAppRunnerOrigin(key, value);
+          }
+          return acc;
+        },
+        {} as Record<string, HttpOrigin>
+      ),
+    };
+    return origins;
+  }
+
+  private createRevalidationQueue() {
+    const queue = new Queue(this, "RevalidationQueue", {
+      fifo: true,
+      receiveMessageWaitTime: Duration.seconds(20),
+    });
+    const consumer = new CdkFunction(this, "RevalidationFunction", {
+      description: "Next.js revalidator",
+      handler: "index.handler",
+      code: Code.fromAsset(this.openNextOutput.additionalProps?.revalidationFunction?.bundle ?? ""),
+      runtime: Runtime.NODEJS_18_X,
+      timeout: Duration.seconds(30),
+    });
+    consumer.addEventSource(new SqsEventSource(queue, { batchSize: 5 }));
+    return queue;
+  }
+
+  private getEnvironment() {
+    return {
+      CACHE_BUCKET_NAME: this.bucket.bucketName,
+      CACHE_BUCKET_KEY_PREFIX: "_cache",
+      CACHE_BUCKET_REGION: Stack.of(this).region,
+      REVALIDATION_QUEUE_URL: this.queue.queueUrl,
+      REVALIDATION_QUEUE_REGION: Stack.of(this).region,
+      CACHE_DYNAMO_TABLE: this.table.tableName,
+      // Those 2 are used only for image optimizer
+      BUCKET_NAME: this.bucket.bucketName,
+      BUCKET_KEY_PREFIX: "_assets",
+    };
+  }
+
+  private grantPermissions(grantable: IGrantable) {
+    this.bucket.grantReadWrite(grantable);
+    this.table.grantReadWriteData(grantable);
+    this.queue.grantSendMessages(grantable);
+  }
+
+  private createFunctionOrigin(key: string, origin: OpenNextFunctionOrigin) {
+    const environment = this.getEnvironment();
+    const fn = new CdkFunction(this, `${key}Function`, {
+      runtime: Runtime.NODEJS_18_X,
+      handler: origin.handler,
+      code: Code.fromAsset(origin.bundle),
+      environment,
+      memorySize: 1024,
+    });
+    const fnUrl = fn.addFunctionUrl({
+      authType: FunctionUrlAuthType.NONE,
+      invokeMode: origin.streaming ? InvokeMode.RESPONSE_STREAM : InvokeMode.BUFFERED,
+    });
+    this.grantPermissions(fn);
+    return new HttpOrigin(Fn.parseDomainName(fnUrl.url));
+  }
 
   // We are using AppRunner because it is the easiest way to demonstrate the new feature.
   // You can use any other container service like ECS, EKS, Fargate, etc.
-	private createAppRunnerOrigin(
-		key: string,
-		origin: OpenNextECSOrigin,
-	): HttpOrigin {
-		const imageAsset = new DockerImageAsset(this, `${key}ImageAsset`, {
-			directory: origin.bundle,
-			// file: origin.dockerfile,
-		});
-		const service = new Service(this, `${key}Service`, {
-			source: AppRunnerSource.fromAsset({
-				asset: imageAsset,
-
-				imageConfiguration: {
-					port: 3000,
-					environmentVariables: this.getEnvironment(),
-				},
-			}),
-			serviceName: key,
-			autoDeploymentsEnabled: false,
-			cpu: Cpu.HALF_VCPU,
-			memory: Memory.ONE_GB,
-			healthCheck: HealthCheck.http({
-				path: "/__health",
-			}),
-		});
-		this.grantPermissions(service);
-		return new HttpOrigin(service.serviceUrl);
-	}
-
-	private createDistribution(origins: Record<string, HttpOrigin | S3Origin>) {
-		const cloudfrontFunction = new CloudfrontFunction(this, 'OpenNextCfFunction', {
-			code: FunctionCode.fromInline(`
+  private createAppRunnerOrigin(key: string, origin: OpenNextECSOrigin): HttpOrigin {
+    const imageAsset = new DockerImageAsset(this, `${key}ImageAsset`, {
+      directory: origin.bundle,
+      // file: origin.dockerfile,
+    });
+    const service = new Service(this, `${key}Service`, {
+      source: AppRunnerSource.fromAsset({
+        asset: imageAsset,
+
+        imageConfiguration: {
+          port: 3000,
+          environmentVariables: this.getEnvironment(),
+        },
+      }),
+      serviceName: key,
+      autoDeploymentsEnabled: false,
+      cpu: Cpu.HALF_VCPU,
+      memory: Memory.ONE_GB,
+      healthCheck: HealthCheck.http({
+        path: "/__health",
+      }),
+    });
+    this.grantPermissions(service);
+    return new HttpOrigin(service.serviceUrl);
+  }
+
+  private createDistribution(origins: Record<string, HttpOrigin | S3Origin>) {
+    const cloudfrontFunction = new CloudfrontFunction(this, "OpenNextCfFunction", {
+      code: FunctionCode.fromInline(`
 			function handler(event) {
 				var request = event.request;
 				request.headers["x-forwarded-host"] = request.headers.host;
 				return request;
 			}
-			`)
-		})
-		const fnAssociations = [
-			{
-				function: cloudfrontFunction ,
-				eventType: FunctionEventType.VIEWER_REQUEST,
-			},
-		]
-
-		const distribution = new Distribution(this, "OpenNextDistribution", {
-			defaultBehavior: {
-				origin: origins.default,
-				viewerProtocolPolicy: ViewerProtocolPolicy.REDIRECT_TO_HTTPS,
-				allowedMethods: AllowedMethods.ALLOW_GET_HEAD_OPTIONS,
-				cachedMethods: CachedMethods.CACHE_GET_HEAD_OPTIONS,
-				cachePolicy: this.serverCachePolicy,
-				originRequestPolicy: OriginRequestPolicy.ALL_VIEWER_EXCEPT_HOST_HEADER,
-				functionAssociations: fnAssociations
-			},
-			additionalBehaviors: this.openNextOutput.behaviors
-				.filter((b) => b.pattern !== "*")
-				.reduce(
-					(acc, behavior) => {
-						return {
-							...acc,
-							[behavior.pattern]: {
-								origin: behavior.origin
-									? origins[behavior.origin]
-									: origins.default,
-								viewerProtocolPolicy: ViewerProtocolPolicy.REDIRECT_TO_HTTPS,
-								allowedMethods: AllowedMethods.ALLOW_GET_HEAD_OPTIONS,
-								cachedMethods: CachedMethods.CACHE_GET_HEAD_OPTIONS,
-								cachePolicy:
-									behavior.origin === "s3"
-										? this.staticCachePolicy
-										: this.serverCachePolicy,
-								originRequestPolicy: 
-									behavior.origin === "s3" 
-										? undefined 
-										: OriginRequestPolicy.ALL_VIEWER_EXCEPT_HOST_HEADER,
-								functionAssociations: fnAssociations
-							},
-						};
-					},
-					{} as Record<string, BehaviorOptions>,
-				),
-		});
-		return distribution;
-	}
-
-	private createServerCachePolicy() {
-		return new CachePolicy(this, "OpenNextServerCachePolicy", {
-			queryStringBehavior: CacheQueryStringBehavior.all(),
-			headerBehavior: CacheHeaderBehavior.allowList(
-				"accept",
-				"accept-encoding",
-				"rsc",
-				"next-router-prefetch",
-				"next-router-state-tree",
-				"next-url",
-				"x-prerender-revalidate",
-			),
-			cookieBehavior: CacheCookieBehavior.none(),
-			defaultTtl: Duration.days(0),
-			maxTtl: Duration.days(365),
-			minTtl: Duration.days(0),
-		});
-	}
-
-	private createStaticCachePolicy() {
-		return CachePolicy.CACHING_OPTIMIZED;
-	}
+			`),
+    });
+    const fnAssociations = [
+      {
+        function: cloudfrontFunction,
+        eventType: FunctionEventType.VIEWER_REQUEST,
+      },
+    ];
+
+    const distribution = new Distribution(this, "OpenNextDistribution", {
+      defaultBehavior: {
+        origin: origins.default,
+        viewerProtocolPolicy: ViewerProtocolPolicy.REDIRECT_TO_HTTPS,
+        allowedMethods: AllowedMethods.ALLOW_GET_HEAD_OPTIONS,
+        cachedMethods: CachedMethods.CACHE_GET_HEAD_OPTIONS,
+        cachePolicy: this.serverCachePolicy,
+        originRequestPolicy: OriginRequestPolicy.ALL_VIEWER_EXCEPT_HOST_HEADER,
+        functionAssociations: fnAssociations,
+      },
+      additionalBehaviors: this.openNextOutput.behaviors
+        .filter((b) => b.pattern !== "*")
+        .reduce(
+          (acc, behavior) => {
+            return {
+              ...acc,
+              [behavior.pattern]: {
+                origin: behavior.origin ? origins[behavior.origin] : origins.default,
+                viewerProtocolPolicy: ViewerProtocolPolicy.REDIRECT_TO_HTTPS,
+                allowedMethods: AllowedMethods.ALLOW_GET_HEAD_OPTIONS,
+                cachedMethods: CachedMethods.CACHE_GET_HEAD_OPTIONS,
+                cachePolicy: behavior.origin === "s3" ? this.staticCachePolicy : this.serverCachePolicy,
+                originRequestPolicy:
+                  behavior.origin === "s3" ? undefined : OriginRequestPolicy.ALL_VIEWER_EXCEPT_HOST_HEADER,
+                functionAssociations: fnAssociations,
+              },
+            };
+          },
+          {} as Record<string, BehaviorOptions>
+        ),
+    });
+    return distribution;
+  }
+
+  private createServerCachePolicy() {
+    return new CachePolicy(this, "OpenNextServerCachePolicy", {
+      queryStringBehavior: CacheQueryStringBehavior.all(),
+      headerBehavior: CacheHeaderBehavior.allowList(
+        "accept",
+        "accept-encoding",
+        "rsc",
+        "next-router-prefetch",
+        "next-router-state-tree",
+        "next-url",
+        "x-prerender-revalidate"
+      ),
+      cookieBehavior: CacheCookieBehavior.none(),
+      defaultTtl: Duration.days(0),
+      maxTtl: Duration.days(365),
+      minTtl: Duration.days(0),
+    });
+  }
+
+  private createStaticCachePolicy() {
+    return CachePolicy.CACHING_OPTIMIZED;
+  }
 }
-
 ```
diff --git a/pages/aws/v2.mdx b/pages/aws/v2.mdx
index 1e7f027..10bfddb 100644
--- a/pages/aws/v2.mdx
+++ b/pages/aws/v2.mdx
@@ -1,11 +1,10 @@
-import { Callout } from 'nextra/components'
+import { Callout } from "nextra/components";
 
 <Callout>
-  OpenNext V2 will be deprecated soon and will not receive new features or updates.
-  
-  We might release security updates if needed. They will be listed on this page.
+  OpenNext V2 will be deprecated soon and will not receive new features or updates. We might release security
+  updates if needed. They will be listed on this page.
 </Callout>
 
 ### Latest Releases
 
-- OpenNext [2.3.9](https://github.com/sst/open-next/releases/tag/v2.3.9)
\ No newline at end of file
+- OpenNext [2.3.9](https://github.com/sst/open-next/releases/tag/v2.3.9)
diff --git a/pages/aws/v2/_meta.json b/pages/aws/v2/_meta.json
index 6d0e932..eed8218 100644
--- a/pages/aws/v2/_meta.json
+++ b/pages/aws/v2/_meta.json
@@ -2,4 +2,4 @@
   "common_issues": "Troubleshooting",
   "inner_workings": "Inner Workings",
   "advanced": "Advanced"
-}
\ No newline at end of file
+}
diff --git a/pages/aws/v2/advanced/_meta.json b/pages/aws/v2/advanced/_meta.json
index 8eb79fc..7591c3e 100644
--- a/pages/aws/v2/advanced/_meta.json
+++ b/pages/aws/v2/advanced/_meta.json
@@ -4,4 +4,4 @@
   "workaround": "Workaround",
   "debugging": "Debugging",
   "contribute": "Contribute"
-}
\ No newline at end of file
+}
diff --git a/pages/aws/v2/advanced/architecture.mdx b/pages/aws/v2/advanced/architecture.mdx
index 651abf7..ea4bbd4 100644
--- a/pages/aws/v2/advanced/architecture.mdx
+++ b/pages/aws/v2/advanced/architecture.mdx
@@ -44,6 +44,7 @@ There are two types of caches in the `.open-next/cache` folder:
 #### Revalidation Table
 
 Create a DynamoDB table with the following configuration:
+
 - Partition key: `tag` (String)
 - Sort key: `path` (String)
 - An index named `revalidate` with the following configuration:
@@ -123,14 +124,14 @@ This ensures that the Lambda handler remains at `index.mjs`.
 
 Create a CloudFront distribution, and dispatch requests to their corresponding handlers (behaviors). The following behaviors are configured:
 
-| Behavior                                                                                                                      | Requests            | CloudFront Function                                                                         | Origin                      |
-| ----------------------------------------------------------------------------------------------------------------------------- | ------------------- | ------------------------------------------------------------------------------------------- | --------------------------- |
-| `/_next/static/*`                                                                                                             | Hashed static files | -                                                                                           | S3 bucket                   |
-| `/favicon.ico`<br />`/my-images/*`<br />[see why](workaround#workaround-public-static-files-served-out-by-server-function-aws-specific) | public assets       | -                                                                                           | S3 bucket                   |
-| `/_next/image`                                                                                                                | Image optimization  | -                                                                                           | image optimization function |
-| `/_next/data/*`                                                                                                               | data requests       | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function             |
-| `/api/*`                                                                                                                      | API                 | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function             |
-| `/*`                                                                                                                          | catch all           | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function             |
+| Behavior                                                                                                                                | Requests            | CloudFront Function                                                                                   | Origin                      |
+| --------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | ----------------------------------------------------------------------------------------------------- | --------------------------- |
+| `/_next/static/*`                                                                                                                       | Hashed static files | -                                                                                                     | S3 bucket                   |
+| `/favicon.ico`<br />`/my-images/*`<br />[see why](workaround#workaround-public-static-files-served-out-by-server-function-aws-specific) | public assets       | -                                                                                                     | S3 bucket                   |
+| `/_next/image`                                                                                                                          | Image optimization  | -                                                                                                     | image optimization function |
+| `/_next/data/*`                                                                                                                         | data requests       | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function             |
+| `/api/*`                                                                                                                                | API                 | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function             |
+| `/*`                                                                                                                                    | catch all           | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function             |
 
 #### Running at edge
 
@@ -138,14 +139,14 @@ The server function can also run at edge locations by configuring it as Lambda@E
 
 To configure the CloudFront distribution:
 
-| Behavior                                                                                                                      | Requests            | CloudFront Function                                                                         | Lambda@Edge     | Origin                      |
-| ----------------------------------------------------------------------------------------------------------------------------- | ------------------- | ------------------------------------------------------------------------------------------- | --------------- | --------------------------- |
-| `/_next/static/*`                                                                                                             | Hashed static files | -                                                                                           | -               | S3 bucket                   |
-| `/favicon.ico`<br />`/my-images/*`<br />[see why](workaround#workaround-public-static-files-served-out-by-server-function-aws-specific) | public assets       | -                                                                                           | -               | S3 bucket                   |
-| `/_next/image`                                                                                                                | Image optimization  | -                                                                                           | -               | image optimization function |
-| `/_next/data/*`                                                                                                               | data requests       | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function | -                           |
-| `/api/*`                                                                                                                      | API                 | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function | -                           |
-| `/*`                                                                                                                          | catch all           | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function | -                           |
+| Behavior                                                                                                                                | Requests            | CloudFront Function                                                                                   | Lambda@Edge     | Origin                      |
+| --------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | ----------------------------------------------------------------------------------------------------- | --------------- | --------------------------- |
+| `/_next/static/*`                                                                                                                       | Hashed static files | -                                                                                                     | -               | S3 bucket                   |
+| `/favicon.ico`<br />`/my-images/*`<br />[see why](workaround#workaround-public-static-files-served-out-by-server-function-aws-specific) | public assets       | -                                                                                                     | -               | S3 bucket                   |
+| `/_next/image`                                                                                                                          | Image optimization  | -                                                                                                     | -               | image optimization function |
+| `/_next/data/*`                                                                                                                         | data requests       | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function | -                           |
+| `/api/*`                                                                                                                                | API                 | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function | -                           |
+| `/*`                                                                                                                                    | catch all           | set `x-forwarded-host`<br />[see why](workaround#workaround-set-x-forwarded-host-header-aws-specific) | server function | -                           |
 
 #### Revalidation function
 
@@ -172,4 +173,4 @@ Read more on [how warming works](/aws/v2/inner_workings/warming).
 This function is used to populate the revalidation table. It is a custom resource handler from the cdk see [here](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.custom_resources.AwsCustomResource.html). Ensure the function is configured as follows:
 
 - Set the `CACHE_DYNAMO_TABLE` environment variable with the value being the name of the DynamoDB table where the revalidation table is stored.
-- Grant `dynamodb:PutItem` permission to allow the function to write to the DynamoDB table.
\ No newline at end of file
+- Grant `dynamodb:PutItem` permission to allow the function to write to the DynamoDB table.
diff --git a/pages/aws/v2/advanced/debugging.mdx b/pages/aws/v2/advanced/debugging.mdx
index 41cb8f4..6c6dcc2 100644
--- a/pages/aws/v2/advanced/debugging.mdx
+++ b/pages/aws/v2/advanced/debugging.mdx
@@ -18,4 +18,4 @@ The logs from the warmer function provide insights into the results of the warmi
 
 #### Opening an issue
 
-To help diagnose issues, it's always helpful to provide a reproducible setup when opening an issue. One easy way to do this is to create a pull request (PR) and add a new page to the [benchmark app](#example) located in the `example` folder, which reproduces the issue. The PR will automatically deploy the app to AWS.
\ No newline at end of file
+To help diagnose issues, it's always helpful to provide a reproducible setup when opening an issue. One easy way to do this is to create a pull request (PR) and add a new page to the [benchmark app](#example) located in the `example` folder, which reproduces the issue. The PR will automatically deploy the app to AWS.
diff --git a/pages/aws/v2/advanced/options.mdx b/pages/aws/v2/advanced/options.mdx
index a246736..d21cc69 100644
--- a/pages/aws/v2/advanced/options.mdx
+++ b/pages/aws/v2/advanced/options.mdx
@@ -32,7 +32,7 @@ import { build } from "open-next/build.js";
 await build({
   buildCommand: "pnpm custom:build",
   appPath: "./apps/example-app",
-  buildOutputPath: "./dist/apps/example-app"
+  buildOutputPath: "./dist/apps/example-app",
 });
 ```
 
@@ -58,7 +58,7 @@ This feature is currently **experimental** and needs to be opted into. It can si
 
 #### **Experimental** Streaming support
 
-Enabling this option will enable streaming support for the server function. This is experimental and needs to be opted into. It can significantly decrease the server function's time to first byte. 
+Enabling this option will enable streaming support for the server function. This is experimental and needs to be opted into. It can significantly decrease the server function's time to first byte.
 
 **Do not use this in production**. See [this](/v2/inner_workings/streaming) for more information.
 
@@ -125,4 +125,4 @@ This does a few things:
 It is recommended to **turn off debug mode when building for production** because:
 
 1. Un-minified function code is 2-3X larger than minified code. This will result in longer Lambda cold start times.
-1. Logging the event object on each request can result in a lot of logs being written to AWS CloudWatch. This will result in increased AWS costs.
\ No newline at end of file
+1. Logging the event object on each request can result in a lot of logs being written to AWS CloudWatch. This will result in increased AWS costs.
diff --git a/pages/aws/v2/common_issues.mdx b/pages/aws/v2/common_issues.mdx
index 307fa54..7edf553 100644
--- a/pages/aws/v2/common_issues.mdx
+++ b/pages/aws/v2/common_issues.mdx
@@ -20,4 +20,4 @@ Given how ISR works, while waiting for the revalidation to happen, the page will
 
 AWS Lambda has an unzipped size limit of 250MB. If your app is over this limit, then it is most likely using a node_module library that is too large for serverless or there is a large dev dependency getting bundled.
 For example, `pdfjs` has `canvas` optional dependency which takes up 180MB. For more details, [read me](/aws/v2/common_issues/bundle_size).
-Note: a large bundle size will increase cold start significantly.
\ No newline at end of file
+Note: a large bundle size will increase cold start significantly.
diff --git a/pages/aws/v2/common_issues/bundle_size.mdx b/pages/aws/v2/common_issues/bundle_size.mdx
index 6132df4..31950cd 100644
--- a/pages/aws/v2/common_issues/bundle_size.mdx
+++ b/pages/aws/v2/common_issues/bundle_size.mdx
@@ -1,13 +1,12 @@
-import {Callout} from 'nextra/components'
-
+import { Callout } from "nextra/components";
 
 #### Reducing Bundle Size
 
 Serverless environments are sensitive to bundle size, since it has to download and unzip the contents. To help reduce cold start times as much as possible, you should remove any unnecessary files in the node_modules or report offending dev libraries in this [PR](https://github.com/sst/open-next/pull/242)
 
-
 <Callout type="info" emoji="ℹ️">
-  Next 14+ no longer includes dev dependencies like @swc, esbuild, etc... in the output node_modules, so please upgrade at your earliest convenience.
+  Next 14+ no longer includes dev dependencies like @swc, esbuild, etc... in the output node_modules, so
+  please upgrade at your earliest convenience.
 </Callout>
 
 #### Unzipped size must be smaller than 262144000 bytes
@@ -21,7 +20,8 @@ du -hs .open-next/server-function/node_modules/* | sort -rh
 If your app requires the offending library, then consider moving your business logic of the `api` to its own lambda, eg: `/api/v2` => `Api Lambda`
 
 <Callout type="info" emoji="ℹ️">
-  There is a [PR](https://github.com/sst/open-next/pull/242) to remove some dev dependency from the output node_modules but that requires more testing before it can merge.
+  There is a [PR](https://github.com/sst/open-next/pull/242) to remove some dev dependency from the output
+  node_modules but that requires more testing before it can merge.
 </Callout>
 
 #### Common issues
diff --git a/pages/aws/v2/common_issues/isr.mdx b/pages/aws/v2/common_issues/isr.mdx
index e6a4c39..ea38dbf 100644
--- a/pages/aws/v2/common_issues/isr.mdx
+++ b/pages/aws/v2/common_issues/isr.mdx
@@ -1,7 +1,8 @@
-import {Callout} from 'nextra/components'
+import { Callout } from "nextra/components";
 
 <Callout type="warning" emoji="⚠️">
-  `next/cache` revalidation needs `next@13.5.1` or higher to work properly. If you are using an older version, please upgrade.
+  `next/cache` revalidation needs `next@13.5.1` or higher to work properly. If you are using an older version,
+  please upgrade.
 </Callout>
 
 #### On-demand revalidation
@@ -42,7 +43,7 @@ async function invalidateCloudFrontPaths(paths: string[]) {
           Items: paths,
         },
       },
-    }),
+    })
   );
 }
 ```
@@ -76,13 +77,11 @@ function getByTag(tag: string) {
         ExpressionAttributeValues: {
           ":tag": { S: `${process.env.NEXT_BUILD_ID}/${tag}` },
         },
-      }),
+      })
     );
     return (
       // We need to remove the buildId from the path
-      Items?.map(
-        ({ path: { S: key } }) => key?.replace(`${process.env.NEXT_BUILD_ID}/`, "") ?? "",
-      ) ?? []
+      Items?.map(({ path: { S: key } }) => key?.replace(`${process.env.NEXT_BUILD_ID}/`, "") ?? "") ?? []
     );
   } catch (e) {
     error("Failed to get by tag", e);
@@ -93,7 +92,7 @@ function getByTag(tag: string) {
 
 #### Patch fetch behaviour for ISR. Only for next@13.5.1+
 
-If you use ISR and fetch in your app, you may encounter a bug that makes your revalidate values inconsistent. 
+If you use ISR and fetch in your app, you may encounter a bug that makes your revalidate values inconsistent.
 The issue is that it revalidates using the lowest revalidate of all fetch calls in your page, regardless of their individual values. To fix this bug, you need to modify the fetch function in your root layout component with the following code snippet
 
 ```ts
@@ -105,4 +104,4 @@ export default function RootLayout() {
   store.isOnDemandRevalidate = store.isOnDemandRevalidate && !(process.env.OPEN_NEXT_ISR === 'true');
   return <>...</>;
 }
-```
\ No newline at end of file
+```
diff --git a/pages/aws/v2/inner_workings/isr.mdx b/pages/aws/v2/inner_workings/isr.mdx
index d1444a1..3f6e653 100644
--- a/pages/aws/v2/inner_workings/isr.mdx
+++ b/pages/aws/v2/inner_workings/isr.mdx
@@ -1,4 +1,4 @@
-import { Callout } from 'nextra/components'
+import { Callout } from "nextra/components";
 
 In standalone mode, Next.js prebuilds the ISR cache during the build process. And at runtime, **NextServer** expects this cache locally on the server. This works effectively when the server is run on a single web server machine, sharing the cache across all requests. In a Lambda environment, the cache needs to be housed centrally in a location accessible by all server Lambda function instances. S3 serves as this central location.
 
@@ -20,9 +20,9 @@ To facilitate this:
 4. A new request comes in for the same page after 2 seconds. Cloudfront sends the cached version back to the user and forwards the request to the `server-function`.
 5. If the revalidation is done, the `server-function` will update the cache and send the updated response back to Cloudfront. Subsequent request will then get the updated version. Otherwise, we go back to step 3.
 
-#### Tags 
+#### Tags
 
-Tags are stored in a dynamodb table. 
+Tags are stored in a dynamodb table.
 There is 3 fields in the table: `tag`, `path`, `revalidatedAt`. The `tag` field is the partition key and `path` is the sort key.
 
 We use an index called `revalidate` with `path` as a partition key and `revalidatedAt` as the sort key.
@@ -36,7 +36,10 @@ When we check if a page is stale, we check the `revalidatedAt` value for each re
 #### Cost
 
 <Callout type="warning" emoji="⚠️">
-  Be aware that fetch cache is using S3. `fetch` by default in next is cached, and even for SSR requests, it will be written to S3. This can lead to a lot of S3 requests and can be expensive. You can disable fetch cache by setting `cache` to `no-store` in the `fetch` options. Also see [this workaround](/aws/v2/common_issues/isr#patch-fetch-behaviour-for-isr-only-for-next1351)
+  Be aware that fetch cache is using S3. `fetch` by default in next is cached, and even for SSR requests, it
+  will be written to S3. This can lead to a lot of S3 requests and can be expensive. You can disable fetch
+  cache by setting `cache` to `no-store` in the `fetch` options. Also see [this
+  workaround](/aws/v2/common_issues/isr#patch-fetch-behaviour-for-isr-only-for-next1351)
 </Callout>
 
 `get` will be called on every request to ISR and SSG that are not cached in Cloudfront, and `set` will be called on every revalidation.
@@ -47,6 +50,7 @@ There is also some cost associated to deployment since you need to upload the ca
 For the examples here, let's assume an app route with a 5 minute revalidation delay in us-east-1. This is assuming you get constant traffic to the route (If you get no traffic, you will only pay for the storage cost).
 
 ##### S3
+
 - Each `get` request to the cache will result in at least 1 `GetObject`
 
 ```
@@ -68,22 +72,26 @@ You can then calculate the cost based on your usage and the [S3 pricing](https:/
 For the example, let's consider that that same route has 2 tags and 10 paths and subpath for each tag. This is assuming you get constant traffic to the route.
 
 - Each `revalidateTag` request will result in 1 `Query` in DynamoDB and a `PutItem` for each path associated with the tag, they are grouped in batches of 25 in a `BatchWriteItem` request.
+
 ```
   Assuming you do 1 revalidation per 5 minute
   Query cost - 8,640 request * $0.25 per 1,000,000 read = $0.00216
   BatchWriteItem cost - 86,400 requests * $0.25 per 1,000,000 write = $0.0216
   Total cost - $0.04536 per tag revalidation per month
 ```
+
 - Each `get` request will result in 1 `Query` in DynamoDB
+
 ```
   Query cost - 8,640 request * $0.25 per 1,000,000 read = $0.00216
   Total cost - $0.00216 per route per month
 ```
+
 - Each `set` request will result in 1 `Query` in DynamoDB and a `PutItem` for each tag associated with the path that are not present in DynamoDB, they are grouped in batches of 25 in a `BatchWriteItem` request.
+
 ```
   Query cost - 8,640 request * $0.25 per 1,000,000 read = $0.00216
   Total cost - $0.00216 per route per month
 ```
 
 You can then calculate the cost based on your usage and the [DynamoDB pricing](https://aws.amazon.com/dynamodb/pricing/)
-
diff --git a/pages/aws/v2/inner_workings/plugin.mdx b/pages/aws/v2/inner_workings/plugin.mdx
index 4ce9945..573eb8a 100644
--- a/pages/aws/v2/inner_workings/plugin.mdx
+++ b/pages/aws/v2/inner_workings/plugin.mdx
@@ -3,8 +3,8 @@ import { Callout } from "nextra/components";
 Open-next use esbuild to build the project. Given that we aim to support multiple version of Next and multiple runtime, we developped a plugin to override some parts of our code at build time with an esbuild plugin.
 
 <Callout type="warning" emoji="⚠️">
-  As of now, the plugin is internal and not exposed to the user.
-  We might expose it in the future, but for now, it is used only internally.
+  As of now, the plugin is internal and not exposed to the user. We might expose it in the future, but for
+  now, it is used only internally.
 </Callout>
 
 #### How to use
@@ -17,7 +17,6 @@ You need to create a ts file where you will override the code. Inside this file,
 const test = "test";
 //#endImport
 
-
 //#override import
 // Everything inside here will replace the content of the override with the given id: import
 // To get the id you'll need to look at the file you want to override
diff --git a/pages/aws/v2/inner_workings/streaming.mdx b/pages/aws/v2/inner_workings/streaming.mdx
index e6d259c..0013aac 100644
--- a/pages/aws/v2/inner_workings/streaming.mdx
+++ b/pages/aws/v2/inner_workings/streaming.mdx
@@ -1,16 +1,17 @@
-import { Callout } from 'nextra/components'
+import { Callout } from "nextra/components";
 
 <Callout type="warning" emoji="⚠️">
   Streaming support is **EXTREMELY EXPERIMENTAL**... AWS has updated their runtime in the past which broke streaming... It seems stable now but if they do another rugpull, it could cause your app to break.
 
-  **It's not recommended to use streaming in production.**
+**It's not recommended to use streaming in production.**
+
 </Callout>
 
 Streaming is using the new AWS lambda support for [streaming responses](https://docs.aws.amazon.com/lambda/latest/dg/configuration-response-streaming.html). This allows you to send data to the client as it's generated instead of waiting for the entire response to be generated.
 
 If you want to try streaming you need to set the function url invoke mode to `RESPONSE_STREAM`.
 You'll also need to add a `--streaming` tags to the build cli.
-  
+
 ```bash
 open-next build --streaming
-```
\ No newline at end of file
+```
diff --git a/pages/aws/v2/inner_workings/warming.mdx b/pages/aws/v2/inner_workings/warming.mdx
index 6944adc..35c13e0 100644
--- a/pages/aws/v2/inner_workings/warming.mdx
+++ b/pages/aws/v2/inner_workings/warming.mdx
@@ -44,4 +44,4 @@ $0.00864 + $0.145728288 + $0.0161280288 x 50 = $0.960769728
 
 ```
 
-This cost estimate is based on the `us-east-1` region pricing and does not consider any free tier benefits.
\ No newline at end of file
+This cost estimate is based on the `us-east-1` region pricing and does not consider any free tier benefits.
diff --git a/pages/cloudflare/0.2/_meta.json b/pages/cloudflare/0.2/_meta.json
index 9a7cfe5..53a20a0 100644
--- a/pages/cloudflare/0.2/_meta.json
+++ b/pages/cloudflare/0.2/_meta.json
@@ -4,4 +4,4 @@
   "bindings": "",
   "caching": "",
   "examples": ""
-}
\ No newline at end of file
+}
diff --git a/pages/cloudflare/0.2/bindings.mdx b/pages/cloudflare/0.2/bindings.mdx
index 900e009..f42790d 100644
--- a/pages/cloudflare/0.2/bindings.mdx
+++ b/pages/cloudflare/0.2/bindings.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../../config";
+import { Callout } from "nextra/components";
 
 ### Bindings
 
@@ -17,13 +17,13 @@ You can access [bindings](https://developers.cloudflare.com/workers/runtime-apis
 import { getCloudflareContext } from "@opennextjs/cloudflare";
 
 export async function GET(request) {
-	let responseText = "Hello World";
+  let responseText = "Hello World";
 
-	const myKv = (await getCloudflareContext()).env.MY_KV_NAMESPACE;
-	await myKv.put("foo", "bar");
-	const foo = await myKv.get("foo");
+  const myKv = (await getCloudflareContext()).env.MY_KV_NAMESPACE;
+  await myKv.put("foo", "bar");
+  const foo = await myKv.get("foo");
 
-	return new Response(foo);
+  return new Response(foo);
 }
 ```
 
@@ -56,10 +56,9 @@ You can access context about the incoming request from the [`cf` object](https:/
 ```js
 import { getCloudflareContext } from "@opennextjs/cloudflare";
 
-
 export async function GET(request) {
-	const { env, cf, ctx } = await getCloudflareContext();
+  const { env, cf, ctx } = await getCloudflareContext();
 
-	// ...
+  // ...
 }
 ```
diff --git a/pages/cloudflare/0.2/caching.mdx b/pages/cloudflare/0.2/caching.mdx
index cbeb544..e507e21 100644
--- a/pages/cloudflare/0.2/caching.mdx
+++ b/pages/cloudflare/0.2/caching.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../../config";
+import { Callout } from "nextra/components";
 
 ## Caching
 
@@ -10,7 +10,8 @@ By default, all `fetch()` subrequests made in your Next.js app are cached. Refer
 [The cache persists across deployments](https://nextjs.org/docs/app/building-your-application/caching#data-cache). You are responsible for revalidating/purging this cache.
 
 <Callout>
-Workers KV is eventually consistent, which means that it can take up to 60 seconds for updates to be reflected globally, when using the default TTL of 60 seconds.
+  Workers KV is eventually consistent, which means that it can take up to 60 seconds for updates to be
+  reflected globally, when using the default TTL of 60 seconds.
 </Callout>
 
 ### How to enable caching
diff --git a/pages/cloudflare/0.2/examples.mdx b/pages/cloudflare/0.2/examples.mdx
index 2cdecbb..4fd3469 100644
--- a/pages/cloudflare/0.2/examples.mdx
+++ b/pages/cloudflare/0.2/examples.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../../config";
+import { Callout } from "nextra/components";
 
 ## Examples
 
@@ -13,8 +13,8 @@ npm create cloudflare@latest -- my-next-app --framework=next --experimental
 
 Two basic example apps are included in the repository for `@opennextjs/cloudflare` package:
 
-- [*`create-next-app`*](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/create-next-app) — a Next.js project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
-- [*`api`*](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/api) — a minimal Next.js project with a single API route
+- [_`create-next-app`_](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/create-next-app) — a Next.js project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
+- [_`api`_](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/api) — a minimal Next.js project with a single API route
 
 You can use these to understand how to configure your Next.js app to use `@opennextjs/cloudflare`, or refer to [Get Started](/cloudflare/get-started).
 
diff --git a/pages/cloudflare/0.2/get-started.mdx b/pages/cloudflare/0.2/get-started.mdx
index 803fbe4..ea1482e 100644
--- a/pages/cloudflare/0.2/get-started.mdx
+++ b/pages/cloudflare/0.2/get-started.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../../config";
+import { Callout } from "nextra/components";
 
 ### Get Started
 
@@ -30,7 +30,7 @@ npm install -D wrangler@latest
 ```
 
 <Callout>
-You must use Wrangler version `3.78.10` or later to deploy Next.js apps using `@opennextjs/cloudflare`.
+  You must use Wrangler version `3.78.10` or later to deploy Next.js apps using `@opennextjs/cloudflare`.
 </Callout>
 
 Then, add a [`wrangler.toml`](https://developers.cloudflare.com/workers/wrangler/configuration/) file to the root directory of your Next.js app:
@@ -44,7 +44,10 @@ assets = { directory = ".worker-next/assets", binding = "ASSETS" }
 ```
 
 <Callout>
-As shown above, you must enable the [`nodejs_compat` compatibility flag](https://developers.cloudflare.com/workers/runtime-apis/nodejs/) *and* set your [compatibility date](https://developers.cloudflare.com/workers/configuration/compatibility-dates/) to `2024-09-23` or later, in order for your Next.js app to work with @opennextjs/cloudflare.
+  As shown above, you must enable the [`nodejs_compat` compatibility
+  flag](https://developers.cloudflare.com/workers/runtime-apis/nodejs/) *and* set your [compatibility
+  date](https://developers.cloudflare.com/workers/configuration/compatibility-dates/) to `2024-09-23` or
+  later, in order for your Next.js app to work with @opennextjs/cloudflare.
 </Callout>
 
 `wrangler.toml` is where you configure your Worker and define what resources it can access via [bindings](https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings).
diff --git a/pages/cloudflare/0.2/index.mdx b/pages/cloudflare/0.2/index.mdx
index 02ba3dd..2c39400 100644
--- a/pages/cloudflare/0.2/index.mdx
+++ b/pages/cloudflare/0.2/index.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../../config";
+import { Callout } from "nextra/components";
 
 ## Cloudflare
 
diff --git a/pages/cloudflare/0.3/bindings.mdx b/pages/cloudflare/0.3/bindings.mdx
index ee412f0..d0af91d 100644
--- a/pages/cloudflare/0.3/bindings.mdx
+++ b/pages/cloudflare/0.3/bindings.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../../config";
+import { Callout } from "nextra/components";
 
 ### Bindings
 
@@ -17,13 +17,13 @@ You can access [bindings](https://developers.cloudflare.com/workers/runtime-apis
 import { getCloudflareContext } from "@opennextjs/cloudflare";
 
 export async function GET(request) {
-	let responseText = "Hello World";
+  let responseText = "Hello World";
 
-	const myKv = (await getCloudflareContext()).env.MY_KV_NAMESPACE;
-	await myKv.put("foo", "bar");
-	const foo = await myKv.get("foo");
+  const myKv = (await getCloudflareContext()).env.MY_KV_NAMESPACE;
+  await myKv.put("foo", "bar");
+  const foo = await myKv.get("foo");
 
-	return new Response(foo);
+  return new Response(foo);
 }
 ```
 
@@ -56,10 +56,9 @@ You can access context about the incoming request from the [`cf` object](https:/
 ```js
 import { getCloudflareContext } from "@opennextjs/cloudflare";
 
-
 export async function GET(request) {
-	const { env, cf, ctx } = await getCloudflareContext();
+  const { env, cf, ctx } = await getCloudflareContext();
 
-	// ...
+  // ...
 }
 ```
diff --git a/pages/cloudflare/0.3/caching.mdx b/pages/cloudflare/0.3/caching.mdx
index 5e4688e..47e9168 100644
--- a/pages/cloudflare/0.3/caching.mdx
+++ b/pages/cloudflare/0.3/caching.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../../config";
+import { Callout } from "nextra/components";
 
 ## Caching
 
@@ -14,7 +14,8 @@ Note that [Revalidating](https://nextjs.org/docs/app/building-your-application/d
 Next.js primes the cache at build time. The build time values are serverd by the [Workers Assets](https://developers.cloudflare.com/workers/static-assets/).
 
 <Callout>
-Workers KV is eventually consistent, which means that it can take up to 60 seconds for updates to be reflected globally, when using the default TTL of 60 seconds.
+  Workers KV is eventually consistent, which means that it can take up to 60 seconds for updates to be
+  reflected globally, when using the default TTL of 60 seconds.
 </Callout>
 
 ### How to enable caching
@@ -40,8 +41,8 @@ The binding name used in your app's worker is `NEXT_CACHE_WORKERS_KV`.
   "kv_namespaces": [
     {
       "binding": "NEXT_CACHE_WORKERS_KV",
-      "id": "<BINDING_ID>"
-    }
-  ]
+      "id": "<BINDING_ID>",
+    },
+  ],
 }
 ```
diff --git a/pages/cloudflare/0.3/examples.mdx b/pages/cloudflare/0.3/examples.mdx
index deafb82..d75a1f6 100644
--- a/pages/cloudflare/0.3/examples.mdx
+++ b/pages/cloudflare/0.3/examples.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../../config";
+import { Callout } from "nextra/components";
 
 ## Examples
 
@@ -13,10 +13,10 @@ npm create cloudflare@latest -- my-next-app --framework=next --experimental
 
 Basic example apps are included in the repository for `@opennextjs/cloudflare` package:
 
-- [*`create-next-app`*](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/create-next-app) — a Next.js project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
-- [*`api`*](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/api) — a minimal Next.js project with a single API route
-- [*`middleware`*](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/middleware) — a minimal Next.js project using middleware
-- [*`vercel-blog-starter`*](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/vercel-blog-starter) — a blog project using SSG
+- [_`create-next-app`_](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/create-next-app) — a Next.js project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
+- [_`api`_](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/api) — a minimal Next.js project with a single API route
+- [_`middleware`_](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/middleware) — a minimal Next.js project using middleware
+- [_`vercel-blog-starter`_](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/vercel-blog-starter) — a blog project using SSG
 
 You can use these to understand how to configure your Next.js app to use `@opennextjs/cloudflare`, or refer to [Get Started](/cloudflare/get-started).
 
diff --git a/pages/cloudflare/0.3/get-started.mdx b/pages/cloudflare/0.3/get-started.mdx
index b3b5668..de6091d 100644
--- a/pages/cloudflare/0.3/get-started.mdx
+++ b/pages/cloudflare/0.3/get-started.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../../config";
+import { Callout } from "nextra/components";
 
 ### Get Started
 
@@ -30,19 +30,21 @@ npm install --save-dev wrangler@latest
 ```
 
 <Callout>
-You must use Wrangler version `3.99.0` or later to deploy Next.js apps using `@opennextjs/cloudflare`.
+  You must use Wrangler version `3.99.0` or later to deploy Next.js apps using `@opennextjs/cloudflare`.
 </Callout>
 
 ##### 3. Create a wrangler configuration file
 
-<Callout type='info'>
-This step is optional since `@opennextjs/cloudflare` creates this file for you during the build process (if not already present).
+<Callout type="info">
+  This step is optional since `@opennextjs/cloudflare` creates this file for you during the build process (if
+  not already present).
 </Callout>
 
 A [wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/) is needed for your
 application to be previewed and deployed, it is also where you configure your Worker and define what resources it can access via [bindings](https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings).
 
 You can create one yourself in the root directory of your Next.js app with the name `wrangler.json` and the following content:
+
 ```jsonc
 {
   "$schema": "node_modules/wrangler/config-schema.json",
@@ -66,16 +68,20 @@ You can create one yourself in the root directory of your Next.js app with the n
 ```
 
 <Callout>
-As shown above:
- - You must enable the [`nodejs_compat` compatibility flag](https://developers.cloudflare.com/workers/runtime-apis/nodejs/) *and* set your [compatibility date](https://developers.cloudflare.com/workers/configuration/compatibility-dates/) to `2024-09-23` or later, in order for your Next.js app to work with @opennextjs/cloudflare
- - The `main` and `assets` values should also not be changed unless you modify the build output result in some way
- - You can add a binding named `NEXT_CACHE_WORKERS_KV` to make use of Next.js' caching as described in the [Caching docs](/cloudflare/caching)
+  As shown above: - You must enable the [`nodejs_compat` compatibility
+  flag](https://developers.cloudflare.com/workers/runtime-apis/nodejs/) *and* set your [compatibility
+  date](https://developers.cloudflare.com/workers/configuration/compatibility-dates/) to `2024-09-23` or
+  later, in order for your Next.js app to work with @opennextjs/cloudflare - The `main` and `assets` values
+  should also not be changed unless you modify the build output result in some way - You can add a binding
+  named `NEXT_CACHE_WORKERS_KV` to make use of Next.js' caching as described in the [Caching
+  docs](/cloudflare/caching)
 </Callout>
 
 ##### 4. Add an `open-next.config.ts` file
 
-<Callout type='info'>
-This step is optional since `@opennextjs/cloudflare` creates this file for you during the build process (if not already present).
+<Callout type="info">
+  This step is optional since `@opennextjs/cloudflare` creates this file for you during the build process (if
+  not already present).
 </Callout>
 
 Add a [`open-next.config.ts`](https://opennext.js.org/aws/config) file to the root directory of your Next.js app:
@@ -110,7 +116,8 @@ export default config;
 ```
 
 <Callout>
-To use the `OpenNextConfig` type as illustrated above (which is not necessary), you need to install the `@opennextjs/aws` NPM package as a dev dependency.
+  To use the `OpenNextConfig` type as illustrated above (which is not necessary), you need to install the
+  `@opennextjs/aws` NPM package as a dev dependency.
 </Callout>
 
 ##### 5. Add a `.dev.vars` file
@@ -163,10 +170,11 @@ Uninstalling the [`@cloudflare/next-on-pages`](https://www.npmjs.com/package/@cl
 
 Remove any reference of these packages from your source and configuration files.
 This includes:
- - `setupDevPlatform()` calls in your Next.js config file
- - `getRequestContext` imports from `@cloudflare/next-on-pages` from your source files
-   (those can be replaced with `getCloudflareContext` calls from `@opennextjs/cloudflare`)
- - next-on-pages eslint rules set in your Eslint config file
+
+- `setupDevPlatform()` calls in your Next.js config file
+- `getRequestContext` imports from `@cloudflare/next-on-pages` from your source files
+  (those can be replaced with `getCloudflareContext` calls from `@opennextjs/cloudflare`)
+- next-on-pages eslint rules set in your Eslint config file
 
 ##### 11. Develop locally
 
diff --git a/pages/cloudflare/0.3/index.mdx b/pages/cloudflare/0.3/index.mdx
index 3c5e7c3..79748c6 100644
--- a/pages/cloudflare/0.3/index.mdx
+++ b/pages/cloudflare/0.3/index.mdx
@@ -1,6 +1,6 @@
-import { SITE } from '../../../config';
-import { Callout } from 'nextra/components';
-import WindowsSupport from '../../../shared/WindowsSupport.mdx';
+import { SITE } from "../../../config";
+import { Callout } from "nextra/components";
+import WindowsSupport from "../../../shared/WindowsSupport.mdx";
 
 ## Cloudflare
 
diff --git a/pages/cloudflare/bindings.mdx b/pages/cloudflare/bindings.mdx
index b13fbcf..558fb15 100644
--- a/pages/cloudflare/bindings.mdx
+++ b/pages/cloudflare/bindings.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../config";
+import { Callout } from "nextra/components";
 
 ### Bindings
 
@@ -17,13 +17,13 @@ You can access [bindings](https://developers.cloudflare.com/workers/runtime-apis
 import { getCloudflareContext } from "@opennextjs/cloudflare";
 
 export async function GET(request) {
-	let responseText = "Hello World";
+  let responseText = "Hello World";
 
-	const myKv = getCloudflareContext().env.MY_KV_NAMESPACE;
-	await myKv.put("foo", "bar");
-	const foo = await myKv.get("foo");
+  const myKv = getCloudflareContext().env.MY_KV_NAMESPACE;
+  await myKv.put("foo", "bar");
+  const foo = await myKv.get("foo");
 
-	return new Response(foo);
+  return new Response(foo);
 }
 ```
 
@@ -33,8 +33,8 @@ export async function GET(request) {
 	const context = await getCloudflareContext({ async: true });
 	```
 
-	**WARNING**: During SSG caution is advised since secrets (stored in `.dev.vars` files) and local development
-	values from bindings (like values saved in a local KV) will be used for the pages static generation.
+    **WARNING**: During SSG caution is advised since secrets (stored in `.dev.vars` files) and local development
+    values from bindings (like values saved in a local KV) will be used for the pages static generation.
 
 </Callout>
 
@@ -67,10 +67,9 @@ You can access context about the incoming request from the [`cf` object](https:/
 ```js
 import { getCloudflareContext } from "@opennextjs/cloudflare";
 
-
 export async function GET(request) {
-	const { env, cf, ctx } = getCloudflareContext();
+  const { env, cf, ctx } = getCloudflareContext();
 
-	// ...
+  // ...
 }
 ```
diff --git a/pages/cloudflare/caching.mdx b/pages/cloudflare/caching.mdx
index 759cc3b..aba87d7 100644
--- a/pages/cloudflare/caching.mdx
+++ b/pages/cloudflare/caching.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../config";
+import { Callout } from "nextra/components";
 
 ## Caching
 
@@ -12,7 +12,8 @@ By default, all `fetch()` subrequests made in your Next.js app are cached. Refer
 Next.js primes the cache at build time. The build time values are serverd by the [Workers Assets](https://developers.cloudflare.com/workers/static-assets/).
 
 <Callout>
-Workers KV is eventually consistent, which means that it can take up to 60 seconds for updates to be reflected globally, when using the default TTL of 60 seconds.
+  Workers KV is eventually consistent, which means that it can take up to 60 seconds for updates to be
+  reflected globally, when using the default TTL of 60 seconds.
 </Callout>
 
 ### How to enable caching
@@ -71,9 +72,9 @@ const config: OpenNextConfig = {
 export default config;
 ```
 
-
 <Callout>
-  The `direct` mode for the queue is intended for debugging purposes and is not recommended for use in production. We are actively working on a solution that will be suitable for production.
+  The `direct` mode for the queue is intended for debugging purposes and is not recommended for use in
+  production. We are actively working on a solution that will be suitable for production.
 </Callout>
 
 #### On-Demand Revalidation
diff --git a/pages/cloudflare/community.mdx b/pages/cloudflare/community.mdx
index 212a898..985b961 100644
--- a/pages/cloudflare/community.mdx
+++ b/pages/cloudflare/community.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../config";
+import { Callout } from "nextra/components";
 
 ## Projects from the community
 
diff --git a/pages/cloudflare/examples.mdx b/pages/cloudflare/examples.mdx
index ca3c6bd..bf5167b 100644
--- a/pages/cloudflare/examples.mdx
+++ b/pages/cloudflare/examples.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../config";
+import { Callout } from "nextra/components";
 
 ## Examples
 
@@ -13,10 +13,10 @@ npm create cloudflare@latest -- my-next-app --framework=next --experimental
 
 Basic example apps are included in the repository for `@opennextjs/cloudflare` package:
 
-- [*`create-next-app`*](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/create-next-app) — a Next.js project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
-- [*`api`*](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/api) — a minimal Next.js project with a single API route
-- [*`middleware`*](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/middleware) — a minimal Next.js project using middleware
-- [*`vercel-blog-starter`*](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/vercel-blog-starter) — a blog project using SSG
+- [_`create-next-app`_](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/create-next-app) — a Next.js project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
+- [_`api`_](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/api) — a minimal Next.js project with a single API route
+- [_`middleware`_](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/middleware) — a minimal Next.js project using middleware
+- [_`vercel-blog-starter`_](https://github.com/opennextjs/opennextjs-cloudflare/tree/main/examples/vercel-blog-starter) — a blog project using SSG
 
 You can use these to understand how to configure your Next.js app to use `@opennextjs/cloudflare`, or refer to [Get Started](/cloudflare/get-started).
 
diff --git a/pages/cloudflare/get-started.mdx b/pages/cloudflare/get-started.mdx
index 7252fd4..78b5115 100644
--- a/pages/cloudflare/get-started.mdx
+++ b/pages/cloudflare/get-started.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../config";
+import { Callout } from "nextra/components";
 
 ### Get Started
 
@@ -30,19 +30,21 @@ npm install --save-dev wrangler@latest
 ```
 
 <Callout>
-You must use Wrangler version `3.99.0` or later to deploy Next.js apps using `@opennextjs/cloudflare`.
+  You must use Wrangler version `3.99.0` or later to deploy Next.js apps using `@opennextjs/cloudflare`.
 </Callout>
 
 ##### 3. Create a wrangler configuration file
 
-<Callout type='info'>
-This step is optional since `@opennextjs/cloudflare` creates this file for you during the build process (if not already present).
+<Callout type="info">
+  This step is optional since `@opennextjs/cloudflare` creates this file for you during the build process (if
+  not already present).
 </Callout>
 
 A [wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/) is needed for your
 application to be previewed and deployed, it is also where you configure your Worker and define what resources it can access via [bindings](https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings).
 
 You can create one yourself in the root directory of your Next.js app with the name `wrangler.json` and the following content:
+
 ```jsonc
 {
   "$schema": "node_modules/wrangler/config-schema.json",
@@ -66,16 +68,20 @@ You can create one yourself in the root directory of your Next.js app with the n
 ```
 
 <Callout>
-As shown above:
- - You must enable the [`nodejs_compat` compatibility flag](https://developers.cloudflare.com/workers/runtime-apis/nodejs/) *and* set your [compatibility date](https://developers.cloudflare.com/workers/configuration/compatibility-dates/) to `2024-09-23` or later, in order for your Next.js app to work with @opennextjs/cloudflare
- - The `main` and `assets` values should also not be changed unless you modify the build output result in some way
- - You can add a binding named `NEXT_CACHE_WORKERS_KV` to make use of Next.js' caching as described in the [Caching docs](/cloudflare/caching)
+  As shown above: - You must enable the [`nodejs_compat` compatibility
+  flag](https://developers.cloudflare.com/workers/runtime-apis/nodejs/) *and* set your [compatibility
+  date](https://developers.cloudflare.com/workers/configuration/compatibility-dates/) to `2024-09-23` or
+  later, in order for your Next.js app to work with @opennextjs/cloudflare - The `main` and `assets` values
+  should also not be changed unless you modify the build output result in some way - You can add a binding
+  named `NEXT_CACHE_WORKERS_KV` to make use of Next.js' caching as described in the [Caching
+  docs](/cloudflare/caching)
 </Callout>
 
 ##### 4. Add an `open-next.config.ts` file
 
-<Callout type='info'>
-This step is optional since `@opennextjs/cloudflare` creates this file for you during the build process (if not already present).
+<Callout type="info">
+  This step is optional since `@opennextjs/cloudflare` creates this file for you during the build process (if
+  not already present).
 </Callout>
 
 Add a [`open-next.config.ts`](https://opennext.js.org/aws/config) file to the root directory of your Next.js app:
@@ -110,7 +116,8 @@ export default config;
 ```
 
 <Callout>
-To use the `OpenNextConfig` type as illustrated above (which is not necessary), you need to install the `@opennextjs/aws` NPM package as a dev dependency.
+  To use the `OpenNextConfig` type as illustrated above (which is not necessary), you need to install the
+  `@opennextjs/aws` NPM package as a dev dependency.
 </Callout>
 
 ##### 5. Add a `.dev.vars` file
@@ -159,10 +166,11 @@ Uninstalling the [`@cloudflare/next-on-pages`](https://www.npmjs.com/package/@cl
 
 Remove any reference of these packages from your source and configuration files.
 This includes:
- - `setupDevPlatform()` calls in your Next.js config file
- - `getRequestContext` imports from `@cloudflare/next-on-pages` from your source files
-   (those can be replaced with `getCloudflareContext` calls from `@opennextjs/cloudflare`)
- - next-on-pages eslint rules set in your Eslint config file
+
+- `setupDevPlatform()` calls in your Next.js config file
+- `getRequestContext` imports from `@cloudflare/next-on-pages` from your source files
+  (those can be replaced with `getCloudflareContext` calls from `@opennextjs/cloudflare`)
+- next-on-pages eslint rules set in your Eslint config file
 
 ##### 11. Develop locally
 
@@ -173,6 +181,7 @@ from the `@opennextjs/cloudflare` package. This makes sure that the Next.js dev
 cloudflare adapter and it is necessary for using bindings during local development.
 
 This is an example of a Next.js configuration file calling the utility:
+
 ```js
 // next.config.mjs
 
diff --git a/pages/cloudflare/howtos/NextAuth.mdx b/pages/cloudflare/howtos/NextAuth.mdx
index 7c7fa0f..a8e1066 100644
--- a/pages/cloudflare/howtos/NextAuth.mdx
+++ b/pages/cloudflare/howtos/NextAuth.mdx
@@ -1,4 +1,3 @@
-
 ## [NextAuth.js](https://next-auth.js.org/)
 
 NextAuth.js is an open-source authentication solution for Next.js applications.
diff --git a/pages/cloudflare/howtos/stripeAPI.mdx b/pages/cloudflare/howtos/stripeAPI.mdx
index 621cecf..4c024b3 100644
--- a/pages/cloudflare/howtos/stripeAPI.mdx
+++ b/pages/cloudflare/howtos/stripeAPI.mdx
@@ -1,4 +1,3 @@
-
 ## [Stripe API](https://www.npmjs.com/package/stripe)
 
 When [creating a Stripe object](https://docs.stripe.com/js/initializing), the default http client implementation is based on `node:https` which is not implemented on Workers.
@@ -10,7 +9,6 @@ import Stripe from "stripe";
 
 const stripe = Stripe(STRIPE_API_KEY, {
   // Cloudflare Workers use the Fetch API for their API requests.
-  httpClient: Stripe.createFetchHttpClient()
+  httpClient: Stripe.createFetchHttpClient(),
 });
 ```
-
diff --git a/pages/cloudflare/index.mdx b/pages/cloudflare/index.mdx
index 85993f7..3744766 100644
--- a/pages/cloudflare/index.mdx
+++ b/pages/cloudflare/index.mdx
@@ -1,6 +1,6 @@
-import { SITE } from '../../config';
-import { Callout } from 'nextra/components';
-import WindowsSupport from '../../shared/WindowsSupport.mdx';
+import { SITE } from "../../config";
+import { Callout } from "nextra/components";
+import WindowsSupport from "../../shared/WindowsSupport.mdx";
 
 ## Cloudflare
 
diff --git a/pages/cloudflare/migrate-from-0.2-to-0.3.mdx b/pages/cloudflare/migrate-from-0.2-to-0.3.mdx
index 68160a6..e43347a 100644
--- a/pages/cloudflare/migrate-from-0.2-to-0.3.mdx
+++ b/pages/cloudflare/migrate-from-0.2-to-0.3.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../config";
+import { Callout } from "nextra/components";
 
 ### Migrate from 0.2 to 0.3
 
diff --git a/pages/cloudflare/migrate-from-0.3-to-0.4.mdx b/pages/cloudflare/migrate-from-0.3-to-0.4.mdx
index 81c9df5..12c4b0a 100644
--- a/pages/cloudflare/migrate-from-0.3-to-0.4.mdx
+++ b/pages/cloudflare/migrate-from-0.3-to-0.4.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../config";
+import { Callout } from "nextra/components";
 
 ### Migrate from 0.3 (to 0.4)
 
@@ -13,6 +13,7 @@ with the Next.js dev server. If you don't plan on using the `next dev` command y
 configuration file to import and call the utility.
 
 Example:
+
 ```js
 // next.config.mjs
 
diff --git a/pages/cloudflare/troubleshooting.mdx b/pages/cloudflare/troubleshooting.mdx
index f792339..b0521a5 100644
--- a/pages/cloudflare/troubleshooting.mdx
+++ b/pages/cloudflare/troubleshooting.mdx
@@ -1,5 +1,5 @@
-import { SITE } from '../../config';
-import { Callout } from 'nextra/components';
+import { SITE } from "../../config";
+import { Callout } from "nextra/components";
 
 ## Troubleshooting
 
diff --git a/shared/WindowsSupport.mdx b/shared/WindowsSupport.mdx
index 647b7d1..af51736 100644
--- a/shared/WindowsSupport.mdx
+++ b/shared/WindowsSupport.mdx
@@ -1,12 +1,14 @@
 OpenNext can be used on Windows systems but Windows full support is not guaranteed because:
- - historically the Next.js tooling itself has had Windows support issues
-   (and OpenNext is built on these tools)
- - the OpenNext team has limited capacity and fully supporting Windows (given the point above)
-   has been determined to be a lower priority, thus the effort and testing on Windows is limited
+
+- historically the Next.js tooling itself has had Windows support issues
+  (and OpenNext is built on these tools)
+- the OpenNext team has limited capacity and fully supporting Windows (given the point above)
+  has been determined to be a lower priority, thus the effort and testing on Windows is limited
 
 Given the above, you can develop your application under Windows at your own risk. If you don't have an alternative we
 recommend either:
- - running OpenNext using [WSL2](https://learn.microsoft.com/en-us/windows/wsl/),
- - in a Linux Virtual Machine or
- - develop your application using the standard Next.js tooling and deploy it using OpenNext in CI/CD systems such
-   as [GitHub Actions](https://github.com/features/actions) that run linux/MacOS environments
\ No newline at end of file
+
+- running OpenNext using [WSL2](https://learn.microsoft.com/en-us/windows/wsl/),
+- in a Linux Virtual Machine or
+- develop your application using the standard Next.js tooling and deploy it using OpenNext in CI/CD systems such
+  as [GitHub Actions](https://github.com/features/actions) that run linux/MacOS environments
diff --git a/theme.config.jsx b/theme.config.jsx
index 5557379..3b5a92b 100644
--- a/theme.config.jsx
+++ b/theme.config.jsx
@@ -38,8 +38,7 @@ export default {
         },
       ],
       titleTemplate: "%s - OpenNext",
-      description:
-        frontMatter.description || "Open-source Next.js adapters",
+      description: frontMatter.description || "Open-source Next.js adapters",
       openGraph: {
         titleTemplate: "%s - OpenNext",
         images: [
diff --git a/tsconfig.json b/tsconfig.json
index 64f4de7..fca8dc5 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -1,11 +1,7 @@
 {
   "compilerOptions": {
     "target": "es5",
-    "lib": [
-      "dom",
-      "dom.iterable",
-      "esnext"
-    ],
+    "lib": ["dom", "dom.iterable", "esnext"],
     "allowJs": true,
     "skipLibCheck": true,
     "strict": true,
@@ -19,14 +15,6 @@
     "jsx": "preserve",
     "incremental": true
   },
-  "include": [
-    "next-env.d.ts",
-    "**/*.ts",
-    "**/*.tsx",
-    "pages/index.mdx", 
-    "theme.config.jsx"  
-  ],
-  "exclude": [
-    "node_modules"
-  ]
+  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", "pages/index.mdx", "theme.config.jsx"],
+  "exclude": ["node_modules"]
 }