@nuxt/docs-nightly 4.3.0-29473037.29a5a434 → 4.3.0-29473862.8e12791b

package/1.getting-started/06.styling.md

@@ -95,6 +95,10 @@ pnpm install animate.css
 bun install animate.css
 ```
 
+```bash [deno]
+deno install npm:animate.css
+```
+
 ::
 
 Then you can reference it directly in your pages, layouts and components:

package/1.getting-started/15.prerendering.md

@@ -32,6 +32,10 @@ pnpm nuxt generate
 bun x nuxt generate
 ```
 
+```bash [deno]
+deno x nuxt generate
+```
+
 ::
 
 You can now deploy the `.output/public` directory to any static hosting service or preview it locally with `npx serve .output/public`.

package/1.getting-started/17.testing.md

@@ -768,6 +768,9 @@ pnpm add -D @playwright/test @nuxt/test-utils
 ```bash [bun]
 bun add --dev @playwright/test @nuxt/test-utils
 ```
+```bash [deno]
+deno add --dev npm:@playwright/test npm:@nuxt/test-utils
+```
 ::
 
 You can provide global Nuxt configuration, with the same configuration details as the `setup()` function mentioned earlier in this section.

package/1.getting-started/18.upgrade.md

@@ -28,6 +28,10 @@ pnpm nuxt upgrade
 bun x nuxt upgrade
 ```
 
+```bash [deno]
+deno x nuxt upgrade
+```
+
 ::
 
 ### Nightly Release Channel
@@ -198,6 +202,10 @@ pnpm add nuxt@^4.0.0
 bun add nuxt@^4.0.0
 ```
 
+```bash [deno]
+deno add npm:nuxt@^4.0.0
+```
+
 ::
 
 After upgrading, most Nuxt 4 behaviors are now the default. However, some features can still be configured if you need to maintain backward compatibility during your migration.
@@ -240,6 +248,11 @@ pnpm dlx codemod@0.18.7 nuxt/4/migration-recipe
 bun x codemod@0.18.7 nuxt/4/migration-recipe
 ```
 
+```bash [deno]
+# Using pinned version due to https://github.com/codemod/codemod/issues/1710
+deno x codemod@0.18.7 nuxt/4/migration-recipe
+```
+
 ::
 
 This command will execute all codemods in sequence, with the option to deselect any that you do not wish to run. Each codemod is also listed below alongside its respective change and can be executed independently.

package/2.directory-structure/1.app/1.plugins.md

@@ -253,6 +253,9 @@ pnpm add -D vue-gtag-next
 ```bash [bun]
 bun add -D vue-gtag-next
 ```
+```bash [deno]
+deno add -D npm:vue-gtag-next
+```
 ::
 
 Then create a plugin file:

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

@@ -112,8 +112,6 @@ For example, you can define a custom handler utility that wraps the original han
 **Example:**
 
 ```ts [server/utils/handler.ts]
-import type { EventHandler, EventHandlerRequest } from 'h3'
-
 export const defineWrappedResponseHandler = <T extends EventHandlerRequest, D> (
   handler: EventHandler<T, D>,
 ): EventHandler<T, D> =>
@@ -129,6 +127,7 @@ export const defineWrappedResponseHandler = <T extends EventHandlerRequest, D> (
     }
   })
 ```
+
 ```ts [server/api/hello.get.ts]
 export default defineWrappedResponseHandler(event => 'hello world')
 ```

package/3.guide/1.concepts/8.typescript.md

@@ -27,6 +27,10 @@ To enable type-checking at build or development time, install `vue-tsc` and `typ
   bun add -D vue-tsc typescript
   ```
 
+  ```bash [deno]
+  deno add -D npm:vue-tsc npm:typescript
+  ```
+
 ::
 
 Then, run [`nuxt typecheck`](/docs/4.x/api/commands/typecheck) command to check your types:

package/3.guide/5.recipes/2.vite-plugin.md

@@ -26,6 +26,10 @@ First, we need to install the Vite plugin, for our example, we'll use `@rollup/p
   bun add @rollup/plugin-yaml
   ```
 
+  ```bash [deno]
+  deno add npm:@rollup/plugin-yaml
+  ```
+
 ::
 
 Next, we need to import and add it to our [`nuxt.config.ts`](/docs/4.x/directory-structure/nuxt-config) file:

package/5.community/4.contribution.md

@@ -172,7 +172,7 @@ We recommend using [VS Code](https://code.visualstudio.com) along with the [ESLi
 
 #### No Prettier
 
-Since ESLint is already configured to format the code, there is no need to duplicate the functionality with Prettier. To format the code, you can run `yarn lint --fix`, `pnpm lint --fix`, or `bun run lint --fix` or referring the [ESLint section](/docs/4.x/community/contribution#use-eslint) for IDE Setup.
+Since ESLint is already configured to format the code, there is no need to duplicate the functionality with Prettier. To format the code, you can run `yarn lint --fix`, `pnpm lint --fix`, `bun run lint --fix`, or `deno run lint --fix` or referring the [ESLint section](/docs/4.x/community/contribution#use-eslint) for IDE Setup.
 
 If you have Prettier installed in your editor, we recommend you disable it when working on the project to avoid conflict.
 

package/6.bridge/1.overview.md

@@ -46,6 +46,10 @@ pnpm install
 bun install
 ```
 
+```bash [deno]
+deno install
+```
+
 ::
 
 ::note
@@ -74,6 +78,10 @@ pnpm add -D @nuxt/bridge nuxi
 bun add -D @nuxt/bridge nuxi
 ```
 
+```bash [deno]
+deno add -D npm:@nuxt/bridge npm:nuxi
+```
+
 ::
 
 ### Update `nuxt.config`

package/6.bridge/8.nitro.md

@@ -45,6 +45,10 @@ pnpm add -D nuxi
 bun add -D nuxi
 ```
 
+```bash [deno]
+deno add -D npm:nuxi
+```
+
 ::
 
 ### Nuxi

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "4.3.0-29473037.29a5a434",
+  "version": "4.3.0-29473862.8e12791b",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",