You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20-12Lines changed: 20 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,13 +11,13 @@ OpenNext takes the Next.js build output and converts it into a package that can
11
11
12
12
OpenNext aims to support all Next.js 13 features. Some features are work in progress. Please open a [new issue](/issues/new) to let us know!
13
13
14
-
[x] API routes
15
-
[x] Dynamic routes
16
-
[x] Static site generation (SSG)
17
-
[x] Server-side rendering (SSR)
18
-
[x] Incremental static regeneration (ISR)
19
-
[] Image optimization (work in progress)
20
-
[] Middleware (work in progress)
14
+
-[x] API routes
15
+
-[x] Dynamic routes
16
+
-[x] Static site generation (SSG)
17
+
-[x] Server-side rendering (SSR)
18
+
-[x] Incremental static regeneration (ISR)
19
+
-[ ] Image optimization (work in progress)
20
+
-[ ] Middleware (work in progress)
21
21
22
22
## Quick start
23
23
@@ -27,6 +27,14 @@ Naviate to your Next.js app
27
27
cd my-next-app
28
28
```
29
29
30
+
Ensure the [`standalone` output](https://nextjs.org/docs/advanced-features/output-file-tracing#automatically-copying-traced-files) is enabled in your `next.config.js`:
31
+
32
+
```ts
33
+
module.exports= {
34
+
output: "standalone",
35
+
};
36
+
```
37
+
30
38
Build app
31
39
32
40
```bash
@@ -87,16 +95,16 @@ Then `open-next` transforms `@vercel/next`'s build output into a format that can
87
95
88
96
In the `example` folder, you can find a benchmark Next.js app. Here is a link deployed using SST's [`NextjsSite`](https://docs.sst.dev/constructs/NextjsSite) construct. It contains a handful of pages. Each page aims to test a single Next.js feature.
89
97
90
-
## Opening an issue
91
-
92
-
Create a PR and add a new page to the benchmark app in `example` with the issue.
93
-
94
-
### Debugging
98
+
## Debugging
95
99
96
100
You can find the server log in the AWS CloudWatch console of the **region you deployed to**.
97
101
98
102
You can find the middleware log in the AWS CloudWatch console of the **region you are physically close to**. For example, if you deployed your app to `us-east-1` and you are in London, it's likely you will find the logs in `eu-west-2`.
99
103
104
+
## Opening an issue
105
+
106
+
Create a PR and add a new page to the benchmark app in `example` with the issue.
107
+
100
108
## FAQ
101
109
102
110
#### Why use the `@vercel/next` package for building the Next.js app?
0 commit comments