-
Notifications
You must be signed in to change notification settings - Fork 168
Link to OpenNext from next-on-pages readme #884
Conversation
🦋 Changeset detectedLatest commit: b9237d4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
🧪 Prereleases are available for testing 🧪 @cloudflare/next-on-pagesYou can install this latest build in your project with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/11092051431/npm-package-next-on-pages-884@cloudflare/eslint-plugin-next-on-pagesYou can install this latest build in your project with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/11092051431/npm-package-eslint-plugin-next-on-pages-884 |
Co-authored-by: James Anderson <james@eli.cx>
| > [!NOTE] | ||
| > You may want to consider using [`@opennextjs/cloudflare`](https://opennext.js.org/cloudflare), which allows you to build and deploy Next.js apps to [Cloudflare Workers](https://developers.cloudflare.com/workers/static-assets/), use [Node.js APIs](https://developers.cloudflare.com/workers/runtime-apis/nodejs/) that Cloudflare Workers supports, and enables additional Next.js features like Incremental Static Regeneration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like this should say that it's the recommended method and discourage using Pages considering it will be slowly phased out 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure we are quite at the place to say that @opennextjs/cloudflare is the recommended solution; it is still pre-alpha. But I agree that once it begins to stabilize, this is the message we should be sending.
| > [!NOTE] | ||
| > You may want to consider using [`@opennextjs/cloudflare`](https://opennext.js.org/cloudflare), which allows you to build and deploy Next.js apps to [Cloudflare Workers](https://developers.cloudflare.com/workers/static-assets/), use [Node.js APIs](https://developers.cloudflare.com/workers/runtime-apis/nodejs/) that Cloudflare Workers supports, and enables additional Next.js features like Incremental Static Regeneration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure we are quite at the place to say that @opennextjs/cloudflare is the recommended solution; it is still pre-alpha. But I agree that once it begins to stabilize, this is the message we should be sending.
|
#986 updated the readme and added a link to the open-next adapter 🙂 |
@opennextjs/cloudflarerefs cloudflare/cloudflare-docs#17196