merge latest v3 changes

Author: benmccann

CHANGELOG.md

@@ -1981,7 +1981,7 @@ Check [release notes](https://github.com/nitrojs/nitro/releases/tag/v2.11.0)
 - Nested fetch calls with incoming headers and context in event context ([learn more](https://github.com/nitrojs/nitro/pull/930))
 - Binary and Raw storage operations support ([learn more](https://github.com/unjs/unstorage/pull/141))
 - [Cloudflare] Exposed `event.context.cf` ([learn more](https://github.com/nitrojs/nitro/pull/927))
-- Built-in session support ([learn more](https://github.com/unjs/h3/pull/315))
+- Built-in session support ([learn more](https://github.com/h3js/h3/pull/315))
 
 ### 🚀 Enhancements
 

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+CODE_OF_CONDUCT.md.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,65 @@
+# Contribution Guide
+
+<!-- https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors -->
+
+> All contributors lead the growth of Nitro - including you!
+
+## Discussions
+
+You can involve in discussions using:
+
+- [Github Discussions](discussions)
+- [Nitro Discord](https://discord.nitro.build)
+
+## Contribute to the Code
+
+> [!IMPORTANT]
+> Please discuss your ideas with the maintainers before opening a pull request.
+
+### Local Development
+
+- Clone the [`nitrojs/nitro`](https://github.com/nitrojs/nitro) git repository.
+- Install the latest LTS version of [Node.js](https://nodejs.org/en/) (v22+).
+- Enable [corepack](https://github.com/nodejs/corepack) using `corepack enable` (run `npm i -g corepack` if it's not available).
+- Install dependencies using `pnpm install`.
+- Build the project in stub mode using `pnpm build --stub`.
+- Run the playground with `pnpm nitro dev ./playground` to verify changes.
+- Add, modify, and run tests using `pnpm test`.
+  - Tip: Run `pnpm vitest test/presets/node.test.ts` for quick testing.
+
+## Reporting Issues
+
+You might encounter a bug while using Nitro.
+
+Although we aim to resolve all known issues, new bugs can emerge over time. Your bug report helps us find and fix them faster — even if you're unable to fix the underlying code yourself.
+
+Here’s how to report a bug effectively:
+
+### Ensure It's a Bug
+
+Sometimes what seems like a bug may actually be expected behavior or a missing feature. Make sure you’re reporting an actual bug by creating a minimal nitro project and reducing scope.
+
+### Create a Minimal Reproduction
+
+Please create a minimal reproduction using the Nitro starter templates.
+
+Sometimes, bugs originate from another layer — not Nitro itself. A minimal reproduction helps identify the source and speeds up debugging.
+
+Use one of the following templates to reproduce the issue:
+
+- [Stackblitz Template](https://stackblitz.com/fork/github/nitrojs/nitro-starter)
+- [Nitro Starter Repo](https://github.com/nitrojs/nitro-starter)
+
+If your bug involves a higher-level framework like [Nuxt](https://nuxt.com), please report it there. Maintainers will help narrow it down to a Nitro-level issue if needed.
+
+### Search Existing Issues and Discussions
+
+Before creating a new issue, search existing [issues](https://github.com/nitrojs/nitro/issues) and [discussions](https://github.com/nitrojs/nitro/discussions) to see if your bug has already been reported.
+
+If it has already been reported:
+- Add a 👍 reaction to the original post (instead of commenting "me too" or "when will it be fixed").
+- If you can provide additional context or a better/smaller reproduction, please share it.
+
+> [!NOTE]
+> If the issue seems related but different or old or already closed, it's **better to open a new issue**. Maintainers will merge similar issues if needed.
+

README.md

@@ -2,8 +2,8 @@
 
 <!-- automd:badges -->
 
-[![npm version](https://flat.badgen.net/npm/v/nitropack)](https://npmjs.com/package/nitropack)
-[![npm downloads](https://flat.badgen.net/npm/dm/nitropack)](https://npmjs.com/package/nitropack)
+[![npm version](https://img.shields.io/npm/v/nitro)](https://npmjs.com/package/nitro)
+[![npm downloads](https://img.shields.io/npm/dm/nitro)](https://npm.chart.dev/nitro)
 
 <!-- /automd -->
 
@@ -16,18 +16,7 @@ Check [migration guide](./docs/1.guide/00.migration.md) for migrating from Nitro
 
 ## Contribution
 
-<details>
-  <summary>Local development</summary>
-
-- Clone this repository
-- Install the latest LTS version of [Node.js](https://nodejs.org/en/)
-- Enable [Corepack](https://github.com/nodejs/corepack) using `corepack enable`
-- Install dependencies using `pnpm install`
-- Run tests using `pnpm dev` or `pnpm test`
-
-</details>
-
-<!-- /automd -->
+Please check [Contribution guide](CONTRIBUTING.md).
 
 ## License
 

automd.config.ts

@@ -0,0 +1,23 @@
+export default {
+  input: ["README.md", "docs/**/*.md"],
+  generators: {
+    compatDate: {
+      async generate(ctx) {
+        const { compatibilityChanges } = await import("./lib/meta.mjs");
+
+        const table = [
+          "| Compatibility date | Platform | Description |",
+          "|------|----------|-------------|",
+          ...compatibilityChanges.map(
+            (change) =>
+              `| **≥ ${change.from}** | ${change.platform} | ${change.description} |`
+          ),
+        ];
+
+        return {
+          contents: table.join("\n"),
+        };
+      },
+    },
+  },
+};

docs/.config/automd.config.ts

@@ -0,0 +1 @@
+export { default } from "../../automd.config";

docs/1.guide/0.index.md

@@ -12,7 +12,7 @@ icon: ph:book-open-duotone
 
 ## Intro
 
-Nitro is an open source framework to build web servers using [unjs/h3](https://h3.unjs.io) and lots of built-in features.
+Nitro is an open source framework to build web servers using [h3](https://h3.dev/) and lots of built-in features.
 Nitro automatically makes your code compatible with any [deployment](/deploy) provider and runtime!
 
 > [!NOTE]

docs/1.guide/1.utils.md

@@ -13,9 +13,9 @@ It is because Nitro uses [unjs/unimport](https://github.com/unjs/unimport) to au
 
 ## H3 utils
 
-Nitro enables all [h3 utils](https://h3.unjs.io/utils) as auto imports so you can use `defineEventHandler`, `readBody`, etc. without manually importing them.
+Nitro enables all [h3 utils](https://h3.dev/utils) as auto imports so you can use `defineEventHandler`, `readBody`, etc. without manually importing them.
 
-::read-more{title="H3 Docs" to="https://h3.unjs.io/utils"}
+::read-more{title="H3 Docs" to="https://h3.dev/utils"}
 ::
 
 

docs/1.guide/2.routing.md

@@ -8,13 +8,13 @@ icon: ri:direction-line
 
 ## Event handlers
 
-An [event handler](https://h3.unjs.io/guide/event-handler) is a function that will be bound to a route and executed when the route is matched by the router for an incoming request.
+An [event handler](https://h3.dev/guide/event-handler) is a function that will be bound to a route and executed when the route is matched by the router for an incoming request.
 
-:read-more{to="https://h3.unjs.io/guide/event-handler"}
+:read-more{to="https://h3.dev/guide/event-handler"}
 
 ## Filesystem routing
 
-Nitro supports file-based routing for your API routes (files are automatically mapped to [h3 routes](https://h3.unjs.io/guide/router)). Defining a route is as simple as creating a file inside the `server/api/` or `server/routes/` directory.
+Nitro supports file-based routing for your API routes (files are automatically mapped to [h3 routes](https://h3.dev/guide/router)). Defining a route is as simple as creating a file inside the `server/api/` or `server/routes/` directory.
 
 You can only define one handler per files and you can [append the HTTP method](#specific-request-method) to the filename to define a specific request method.
 
@@ -64,7 +64,7 @@ export default defineEventHandler(() => {
 
 #### Single param
 
-To define a route with params, use the `[<param>]` syntax where `<param>` is the name of the param. The param will be available in the `event.context.params` object or using the `getRouterParam` utility from [unjs/h3](https://h3.unjs.io).
+To define a route with params, use the `[<param>]` syntax where `<param>` is the name of the param. The param will be available in the `event.context.params` object or using the `getRouterParam` utility from [h3](https://h3.dev/).
 
 ```ts [server/routes/hello/[name\\].ts]
 export default defineEventHandler(event => {
@@ -169,7 +169,7 @@ Nitro route middleware can hook into the request lifecycle.
 A middleware can modify the request before it is processed, not after.
 ::
 
-:read-more{to="https://h3.unjs.io/guide/event-handler#middleware"}
+:read-more{to="https://h3.dev/guide/event-handler#middleware"}
 
 Middleware are auto-registered within the `server/middleware/` directory.
 
@@ -196,7 +196,7 @@ export default defineEventHandler((event) => {
 })
 ```
 
-Middleware in `server/middleware/` directory are automatically registered for all routes. If you want to register a middleware for a specific route, see [Object Syntax Event Handler](https://h3.unjs.io/guide/event-handler#object-syntax).
+Middleware in `server/middleware/` directory are automatically registered for all routes. If you want to register a middleware for a specific route, see [Object Syntax Event Handler](https://h3.dev/guide/event-handler#object-syntax).
 
 ::note
 Returning anything from a middleware will close the request and should be avoided! Any returned value from middleware will be the response and further code will not be executed however **this is not recommended to do!**
@@ -269,7 +269,7 @@ export default defineEventHandler((event) => {
 
 ## Error handling
 
-You can use the [utilities available in H3](https://h3.unjs.io/guide/event-handler#error-handling) to handle errors in both routes and middlewares.
+You can use the [utilities available in H3](https://h3.dev/guide/event-handler#error-handling) to handle errors in both routes and middlewares.
 
 The way errors are sent back to the client depends on the route's path. For most routes `Content-Type` is set to `text/html` by default and a simple html error page is delivered. If the route starts with `/api/` (either because it is placed in `api/` or `routes/api/`) the default will change to `application/json` and a JSON object will be sent.
 
@@ -279,7 +279,7 @@ This behaviour can be overridden by some request properties (e.g.: `Accept` or `
 
 Nitro allows you to add logic at the top-level for each route of your configuration. It can be used for redirecting, proxying, caching and adding headers to routes.
 
-It is a map from route pattern (following [unjs/radix3](https://github.com/unjs/rou3/tree/radix3#route-matcher)) to route options.
+It is a map from route pattern (following [rou3](https://github.com/h3js/rou3)) to route options.
 
 When `cache` option is set, handlers matching pattern will be automatically wrapped with `defineCachedEventHandler`. See the [cache guide](/guide/cache) to learn more about this function.
 

docs/1.guide/3.websocket.md

@@ -6,7 +6,7 @@ icon: cib:socket-io
 
 > Nitro natively supports a cross platform WebSocket API
 
-Nitro natively supports runtime agnostic [WebSocket](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket) API using [CrossWS](https://crossws.unjs.io/) and [H3 WebSocket](https://h3.unjs.io/guide/websocket).
+Nitro natively supports runtime agnostic [WebSocket](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket) API using [CrossWS](https://crossws.h3.dev/) and [H3 WebSocket](https://h3.dev/guide/websocket).
 
 :read-more{title="WebSocket in MDN" to="https://developer.mozilla.org/en-US/docs/Web/API/WebSocket"}
 
@@ -46,7 +46,7 @@ Create a websocket handler in `server/routes/_ws.ts`.
 > [!TIP]
 > You can use any route like `server/routes/chatroom.ts` to register upgrade handler on `/chatroom`.
 
-<!-- automd:file code src="../../examples/websocket/routes/_ws.ts" -->
+<!-- automd-disabled:file code src="../../examples/websocket/routes/_ws.ts" -->
 
 ```ts [server/routes/_ws.ts]
 export default defineWebSocketHandler({
@@ -79,12 +79,12 @@ export default defineWebSocketHandler({
 
 Use a client to connect to server. Example: (`server/routes/websocket.ts`)
 
-<!-- automd:file code src="../../examples/websocket/routes/index.ts" -->
+<!-- automd-disabled:file code src="../../examples/websocket/routes/index.ts" -->
 
 ```ts [index.ts]
 export default defineEventHandler(() => {
   return $fetch(
-    "https://raw.githubusercontent.com/unjs/crossws/main/examples/h3/public/index.html"
+    "https://raw.githubusercontent.com/h3js/crossws/main/examples/h3/public/index.html"
   );
 });
 
@@ -132,4 +132,4 @@ eventSource.onmessage = (event) => {
 }
 ```
 
-:read-more{to="https://h3.unjs.io/guide/websocket#server-sent-events-sse" title="SSE guide in H3"}
+:read-more{to="https://h3.dev/guide/websocket#server-sent-events-sse" title="SSE guide in H3"}