🚀 nitro v3

[pi0]

Note

This PR is not to merge but you can overview undergoing major nitro v2...v3 breaking changes which will be mostly breaking changes and removals in the first step.

Note

We will keep backporting fixes as much as possible to the nitro v2 until the community adoption of nitro v3. For non-breaking change improvements, please base PR branches on v2 branch. For proposing breaking changes, you can use main. Most of the upcoming features will land to v2 as well ~> v2.10.0 release tracker

⌛ ETA: (TBA) See this

---

Beta testing via nightly channel

Directly using nitro:

  "devDependencies": {
    "nitro": "npm:nitro-nightly@3x"
  },

Using nitro with other frameworks such as Nuxt:

  "resolutions": {
    "nitropack": "npm:nitropack-nightly@3x"
  },

(use overrides for npm)

---

Roadmap: (breaking changes) [WIP

• Remove deprecated exports (63cc133)
• Remove runtime/* compatibility exports (23c715a)
• Migrate from nitropack to nitro as canonical (context: #2497) (9bdce70)
• Remove /* subpath exports (d12305b)
• Remove legacy externals (5d54ed1)
• Remove legacy webpack dynamic require plugin (ba3ee3c)
• Enable AsyncContext by default (f7e1c46)
• Remove appConfig support (#2526)
• Remove legacy fetch polyfill for Node < 18 (#2527)
• increase generated tsconfig.json strictness (#2533)
• Async app+plugins (Make plugins async #915)
• Disable swr by default for cached functions (Disable swr behavior by default for cached functions #1950)
• Migration notes

Dependencies:

• Upgrade to [email protected] (beta)
• Upgrade to [email protected]
• Upgrade and enable crosswasm v1 (websocket)

[MickL]

May I ask what the status of v3 is? :) I see the last commit is from june.

Our team is considering to use Nitro for a huge project.

[pi0]

@MickL Lots of things happening in h3 v2 right now to unblock last steps. (spoiler: it will be 10x faster no cheating & web apis, expect better testing ways and more)

[MickL]

Sounds amazing! Better testing would be huge.

Any ETA on h3 v2 and Nitro v3 from todays perspective?

[Dino-Kupinic]

Sounds amazing! Better testing would be huge.

Any ETA on h3 v2 and Nitro v3 from todays perspective?

Curious as well! 10x speed and Web APIs sound awesome

[bernhardberger]

@pi0 you may want to update the ETA in the first post as ut kinda causes confusion on some social platforms. I think Nuxt already removed their ETA too.

[MickL]

Is it correct that Nitro v3 is in beta? 😍

[MickL]

@corbinu Why did you downvote? Latest npm release is named 3.0.0-beta-28796231.359af68d so I guess it is in beta?

[blouflashdb]

Is v3 still being worked on?

[Makkalay]

Is v3 still being worked on?

You don't like v2? It's Christmas! No one work in that time :)

[pi0]

Hi all. I can assure you we are actively working around releases.
(holidays are actually best time for OSS maintainers since we can focus more haha!)

Nitro v2 is active and will include more enhancements in the parallel.

Nitro v3 release is a just milestone to adopt with ecosystem enhancements that require a breaking change to happen. h3 (v2), new cache layer, unstorage v2, and native vite(6) integration are some of the focus areas outside of this PR. This PR, is simply a placeholder to track commits.

I plan to release Nitro v3 beta.0 until end of this month but really can't promise as it depends on h3 v2 beta release and in parallel working to actively maintain current stable versions across nitro and unjs.

[MickL]

Thanks for the update!

I think what people dont see is the huge ecosystem around Nitro where a lot of things are happening, and eventually all of them will end up to form Nitro v3.

Btw you said Nitro will have significant performance improvements, sounded to me more than just adapting to breaking changes :)

Personally i was hoping for route roules to be fixed #2340 and some more testing utilities. But I am very excited for all the improvements that have been made! Sounds like a nice christmas present :)

[malsatin]

I personally wait for the Nitro v3, because I've heard it is the blocker for Nuxt v4 release.