nuxt/nuxt (@nuxt/kit)
### [`v3.7.0`](https://togithub.com/nuxt/nuxt/releases/tag/v3.7.0)
[Compare Source](https://togithub.com/nuxt/nuxt/compare/v3.6.5...v3.7.0)
#### 👀 Highlights
##### 🐣 A New CLI
We've refactored `nuxi` using [unjs/citty](http://github.com/unjs/citty) and this marks the first Nuxt release that depends on the new version, safely in its own repository. We have grand plans for this - check out some of the features + roadmap discussions in [nuxt/cli](https://togithub.com/nuxt/cli) and please feel free to contribute!
- Project Goals
- Feedbacks and Ideas
- The journey of Nuxt CLI Generations
Nuxi is now decoupled from the main `nuxt` version - we plan to iterate and release nuxi more quickly in future so you can expect new things coming soon!
##### 🕸️ Native Web Streams and `Response`
With improvements in [unjs/h3](https://togithub.com/unjs/h3) and [unjs/nitro](https://togithub.com/unjs/nitro), it's now possible to directly return a `Response` object from server routes, meaning it's *also* possible to return and handle streams natively in Nuxt.
👉 Check out the full detail in the [unjs/h3](https://togithub.com/unjs/h3/releases) and [unjs/nitro](https://togithub.com/unjs/nitro/releases) release notes.
##### 🔥 HTML Rendering Optimisations
This release comes with a couple of improvements in rendering HTML responses from the server. We now determine whether to preload/prefetch resources at build time (so you can customise this in the `build:manifest` hook). We also now manage rendering the HTML for them directly in `unhead` ([#22179](https://togithub.com/nuxt/nuxt/pull/22179)), which means you can configure the *order* for ``, ``, ` Githubissues.
Githubissues is a development platform for aggregating issues.
This PR contains the following updates:
3.6.5
->3.7.0
3.6.5
->3.7.0
Release Notes
nuxt/nuxt (@nuxt/kit)
### [`v3.7.0`](https://togithub.com/nuxt/nuxt/releases/tag/v3.7.0) [Compare Source](https://togithub.com/nuxt/nuxt/compare/v3.6.5...v3.7.0) #### 👀 Highlights ##### 🐣 A New CLI We've refactored `nuxi` using [unjs/citty](http://github.com/unjs/citty) and this marks the first Nuxt release that depends on the new version, safely in its own repository. We have grand plans for this - check out some of the features + roadmap discussions in [nuxt/cli](https://togithub.com/nuxt/cli) and please feel free to contribute! - Project Goals - Feedbacks and Ideas - The journey of Nuxt CLI Generations Nuxi is now decoupled from the main `nuxt` version - we plan to iterate and release nuxi more quickly in future so you can expect new things coming soon! ##### 🕸️ Native Web Streams and `Response` With improvements in [unjs/h3](https://togithub.com/unjs/h3) and [unjs/nitro](https://togithub.com/unjs/nitro), it's now possible to directly return a `Response` object from server routes, meaning it's *also* possible to return and handle streams natively in Nuxt. 👉 Check out the full detail in the [unjs/h3](https://togithub.com/unjs/h3/releases) and [unjs/nitro](https://togithub.com/unjs/nitro/releases) release notes. ##### 🔥 HTML Rendering Optimisations This release comes with a couple of improvements in rendering HTML responses from the server. We now determine whether to preload/prefetch resources at build time (so you can customise this in the `build:manifest` hook). We also now manage rendering the HTML for them directly in `unhead` ([#22179](https://togithub.com/nuxt/nuxt/pull/22179)), which means you can configure the *order* for ``, ``, ` Githubissues.