nrwl / nx

Smart Monorepos · Fast CI
https://nx.dev
MIT License
23.75k stars 2.37k forks source link

[NextJS] Add Next 15 support #28586

Open gperdomor opened 1 month ago

gperdomor commented 1 month ago

Current Behavior

Next generator generate apps with next 14.2.3 is used

Expected Behavior

Next generator should generate apps with next 15.0.0

GitHub Repo

No response

Steps to Reproduce

N/A

Nx Report

N/A

Failure Logs

No response

Package Manager Version

No response

Operating System

Additional Information

No response

Coly010 commented 4 weeks ago

@gperdomor thanks for the issue. This is already on our radar. However, given that since Next 15 released there have been a ton of bug fixes that have shipped to Next 15 patch releases, it might be prudent to wait a little bit longer for Next to be stable (https://github.com/vercel/next.js/commits/canary/)

armingdev commented 3 weeks ago

@gperdomor thanks for the issue. This is already on our radar. However, given that since Next 15 released there have been a ton of bug fixes that have shipped to Next 15 patch releases, it might be prudent to wait a little bit longer for Next to be stable (https://github.com/vercel/next.js/commits/canary/)

I agree that we should wait for the more stable version of NextJS 15, but also there are notable fixes in version 14 and NX should push it to the latest version of NextJS 14. (https://github.com/vercel/next.js/releases/tag/v14.2.16)

The current version has vulnerabilities :

GHSA-gp8f-8m3g-qvj9 7.5 Next. js Cache Poisoning GHSA-g77x-44xx-532m 5.9 Denial of Service condition in Next. js image optimization

ryanolson-aumni commented 2 weeks ago

@gperdomor thanks for the issue. This is already on our radar. However, given that since Next 15 released there have been a ton of bug fixes that have shipped to Next 15 patch releases, it might be prudent to wait a little bit longer for Next to be stable (https://github.com/vercel/next.js/commits/canary/)

It might be prudent, but can't we have the choice to move to Next.js 15? It would be great to add support for it in @nx/next for those that want to experiment with it and start using it.

Reza-tm commented 5 days ago

@gperdomor thanks for the issue. This is already on our radar. However, given that since Next 15 released there have been a ton of bug fixes that have shipped to Next 15 patch releases, it might be prudent to wait a little bit longer for Next to be stable (https://github.com/vercel/next.js/commits/canary/)

It might be prudent, but can't we have the choice to move to Next.js 15? It would be great to add support for it in @nx/next for those that want to experiment with it and start using it.

Isn't there any solution for this ?