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: src/content/docs/pages/framework-guides/nextjs/ssr/supported-features.mdx
+26-29Lines changed: 26 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,9 @@ title: Supported features
4
4
head:
5
5
- tag: title
6
6
content: Supported features
7
-
8
7
---
9
8
10
-
import { Details } from"~/components"
9
+
import { Details } from"~/components";
11
10
12
11
## Supported Next.js versions
13
12
@@ -23,17 +22,17 @@ The [`@opennextjs/cloudflare` adapter](https://opennext.js.org/cloudflare), whic
23
22
24
23
`@opennextjs/cloudflare` is pre 1.0, and still in active development. As it approaches 1.0, it will become the clearly better choice for most Next.js apps, since Next.js has been engineered to only support its Node.js "runtime" for many newly introduced features.
25
24
26
-
Refer to the [OpenNext docs](https://opennext.js.org/cloudflare) and the [Workers vs. Pages compatibility matrix](/workers/static-assets/compatibility-matrix/) for more information to help you decide which to use.
25
+
Refer to the [OpenNext docs](https://opennext.js.org/cloudflare) and the [Workers vs. Pages compatibility matrix](/workers/static-assets/migrate-from-pages/#compatibility-matrix) for more information to help you decide which to use.
27
26
28
27
#### Supported Node.js APIs when using `@cloudflare/next-on-pages`
29
28
30
29
When you use `@cloudflare/next-on-pages`, your Next.js app must use the "edge" runtime from Next.js. The Workers runtime [supports a broad set of Node.js APIs](/workers/runtime-apis/nodejs/) — but [the Next.js Edge Runtime code intentionally constrains this](https://github.com/vercel/next.js/blob/canary/packages/next/src/build/webpack/plugins/middleware-plugin.ts#L820). As a result, only the following Node.js APIs will work in your Next.js app:
31
30
32
-
*`buffer`
33
-
*`events`
34
-
*`assert`
35
-
*`util`
36
-
*`async_hooks`
31
+
-`buffer`
32
+
-`events`
33
+
-`assert`
34
+
-`util`
35
+
-`async_hooks`
37
36
38
37
If you need to use other APIs from Node.js, you should use [`@opennextjs/cloudflare`](https://opennext.js.org/cloudflare) instead.
39
38
@@ -49,41 +48,41 @@ Cloudflare also supports the older [Pages](https://nextjs.org/docs/pages) router
49
48
50
49
[`next.config.js` — app router](https://nextjs.org/docs/app/api-reference/next-config-js) and [\`next.config.js - pages router](https://nextjs.org/docs/pages/api-reference/next-config-js)
@@ -135,14 +134,12 @@ If you use Incremental Static Regeneration (ISR)[^14], `@cloudflare/next-on-page
135
134
136
135
This means that your application will still correctly serve your ISR/prerendered pages (but without the regeneration aspect). If this causes issues for your application, change your pages to use server side rendering (SSR) instead.
137
136
138
-
139
137
<Detailsheader="Background">
140
138
141
139
ISR pages are built by the Vercel CLI to generate Vercel [Prerender Functions](https://vercel.com/docs/build-output-api/v3/primitives#prerender-functions). These are Node.js serverless functions that can be called in the background while serving the page from the cache.
142
140
143
141
It is not possible to use these with Cloudflare Pages and they are not compatible with the [edge runtime](https://nextjs.org/docs/app/api-reference/edge) currently.
144
142
145
-
146
143
</Details>
147
144
148
145
[^14]: [Incremental Static Regeneration (ISR)](https://vercel.com/docs/incremental-static-regeneration) is a rendering mode in Next.js that allows you to automatically cache and periodically regenerate pages with fresh data.
@@ -155,8 +152,8 @@ It does not support dynamic Node.js-based on-demand handling of such routes.
Copy file name to clipboardExpand all lines: src/content/docs/workers/static-assets/migrate-from-pages.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -296,7 +296,7 @@ If you are [using Workers Builds](#builds), ensure you also [configure any varia
296
296
297
297
### Wrangler commands
298
298
299
-
Where previously you used [`wrangler pages dev`](/workers/wrangler/commands/#dev-1) and [`wrangler pages deploy`](/workers/wrangler/commands/#deploy-1), now instead use [`wrangler dev`](/workers/wrangler/commands/#dev) and [`wrangler deploy`](/workers/wrangler/commands/#deploy). Additionally, if you are using a Vite-powered framework, [our new Vite plugin](/workers/local-development/wrangler-vs-vite/) may be able offer you an even simpler development experience.
299
+
Where previously you used [`wrangler pages dev`](/workers/wrangler/commands/#dev-1) and [`wrangler pages deploy`](/workers/wrangler/commands/#deploy-1), now instead use [`wrangler dev`](/workers/wrangler/commands/#dev) and [`wrangler deploy`](/workers/wrangler/commands/#deploy). Additionally, if you are using a Vite-powered framework, [our new Vite plugin](/workers/vite-plugin/) may be able offer you an even simpler development experience.
0 commit comments