@nuxt/docs-nightly 5.0.0-29846154.7802b2c2 → 5.0.0-29850714.87a4b2c4

package/2.directory-structure/1.server.md

@@ -462,12 +462,13 @@ export default useBase('/api/hello', router.handler)
 This is an experimental feature and is available in all environments.
 ::
 
+You can return streams directly from the event handler.
+
 ```ts [server/api/foo.get.ts]
 import fs from 'node:fs'
-import { sendStream } from 'h3'
 
-export default defineEventHandler((event) => {
-  return sendStream(event, fs.createReadStream('/path/to/file'))
+export default defineEventHandler(() => {
+  return fs.createReadStream('/path/to/file')
 })
 ```
 

package/3.guide/4.modules/9.server-compatibility.md

@@ -124,9 +124,38 @@ export default defineNuxtModule({
 })
 ```
 
-::note
-`addServerImports`, `addServerImportsDir` and `addServerTemplate` do not differ between Nitro 2 and 3. If you have code that differs, you can use `getNitroVersion` to conditionally register imports/templates differently.
-::
+### Other Variants
+
+For anything else that points at server code, such as an alias, a type template or an app plugin that reads the server event, you can use `resolveServerVariant` to resolve the variant that is appropriate for this version of Nuxt, or `undefined` if it runs none of them.
+
+`addServerImports` accepts the same variants in `from`.
+
+```ts [module.ts]
+import { addServerImports, createResolver, defineNuxtModule, resolveServerVariant } from '@nuxt/kit'
+
+export default defineNuxtModule({
+  meta: { name: 'my-module' },
+  setup (_options, nuxt) {
+    const { resolve } = createResolver(import.meta.url)
+
+    const someServerFile = resolveServerVariant({
+      nuxt: resolve('./runtime/server'),
+      nitro2: resolve('./runtime/server.legacy'),
+    })
+
+    if (someServerFile) {
+      nuxt.options.alias['#my-module/server'] = someServerFile
+    }
+
+    addServerImports({
+      name: 'verifyToken',
+      from: { nuxt: resolve('./runtime/verify'), nitro2: resolve('./runtime/verify.legacy') },
+    })
+  },
+})
+```
+
+If running with `nitropack` v2, `nitro2` will always be preferred over `nuxt`, and if running with `nitro` v3, `nitro3` will always be preferred over `nuxt`. So, if you need to test the `nuxt` variant, set `server.builder` in your test fixture to a builder that is not Nitro, such as `@nuxt/vite-server`.
 
 ### Declaring What You Cannot Infer
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "5.0.0-29846154.7802b2c2",
+  "version": "5.0.0-29850714.87a4b2c4",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",