use the Cloudflare maintained Next.js template

[petebacondarwin]

---

• Tests
  • Tests included
  • Tests not necessary because: already tested in C3
• Public documentation
  • Cloudflare docs PR(s): TBD - do the CF docs need updating??
  • Documentation not necessary because: this aspect is not mentioned in the docs at https://developers.cloudflare.com/workers/framework-guides/web-apps/nextjs/
• Wrangler V3 Backport
  • Wrangler PR:
  • Not necessary because: C3 is not backported

[changeset-bot]

🦋 Changeset detected

Latest commit: 659cd66

The changes in this PR will be included in the next version bump.

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

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@11132

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@11132

miniflare

npm i https://pkg.pr.new/miniflare@11132

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@11132

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@11132

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@11132

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@11132

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@11132

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@11132

wrangler

npm i https://pkg.pr.new/wrangler@11132

commit: 4000f41

[vicb]

What about moving the template to the OpenNext repo instead?

[petebacondarwin]

That's definitely an option. The question is who will maintain it?
If we put it in OpenNext will it be kept up to date (at least more than than the Cloudflare templates repo)?
If there is no capacity to maintain it in Open Next then at least there is a team that is supposed to be on the hook to maintain the templates repo. I am told that this is a template they do intend to maintain.

[vicb]

I think there are 2 things to take into consideration here:

1. impact on maintenance
2. impact on the users

About the maintenance:

I have never been in contact with that team which is not a positive signal ("not positive" != negative). I just opened the template and see that for ex it doesn't configure binding access in the next config (i.e. calling initOpenNextCloudflareForDev).

Second question is what would framework support be split across different teams?

Last question is how to test changes in the template. It's pretty easy to do that today with a local build of c3. What about moving the template to another repo (either the templates or the open next repo).

Impact on users:

With the current template, users can create a Next app at any Next version as long as it is supported by the adapter (latest 14 minor and any 15 as of today).

The proposed template used a fixed version of Next.

Probably not a huge deal to instantiate 14 or 15 but I can foresee that it becomes a problem when 16 is supported. Implementing the Adapters API will probably imply a different template.