From 26cd8557e28f5b16aae58106e79ea0dbce104055 Mon Sep 17 00:00:00 2001
From: Amp
+
@@ -20,7 +20,7 @@ Unleash Nuxt Developer Experience.
π Introduction |
π‘ Ideas & Suggestions |
πΊοΈ Project Roadmap |
- π Documentation
+ π Documentation
- {{ description }} -
-- {{ section.avatarText }} -
- - -- {{ formatNumber(mod.stats.downloads) }}+ -
-Monthly Downloads
-- {{ formatNumber(mod.stats.stars) }}+ -
-Stars
-
-
-## Pages
-
-Pages tab shows your current routes with some useful information such as what layout or middleware it has, and provides a quick way to navigate between pages. You can also use the textbox to see how each route is matched.
-
-
-
-## Components
-
-Components tab shows all the components you are using in your app and where they are from. You can also search for them and go to the source code.
-
-
-
-Components tab also has a Graph view which you can toggle.
-Graph view also shows the relationship between components, and knows the dependencies of each component.
-
-
-
-You can also inspect your app's DOM tree and see which component is rendering it. Finding the place to make changes are much easier.
-
-
-
-## Imports
-
-Imports tab shows all the auto-imports registered to Nuxt. You can see which files are importing them, and where they are from. Some entries can also provide short descriptions and documentation links.
-
-
-
-## Modules
-
-Modules tab shows all the modules you have installed and their information such as the moduleβs github repository, documentation, version and β¦
-
-
-
-You can install or even remove any Nuxt module with one-click!
-
-## Assets
-
-Assets tab shows your files from the Public directory, you can see the information of selected file with some helpful actions.
-
-You can also upload files with Drag & Drop ability
-
-## Terminals
-
-Terminals tab shows the active terminal processes.
-
-## Runtime Config
-
-Runtime Config tab shows all the runtime config of your project, with the ability to edit them.
-
-## Payload
-
-Payloads tab shows all the state and data payloads of your project.
-
-## Build Analyze
-
-In the Build Analyze tab, you can run analyze build and see the bundle size of your project. it saves the report so you can compare the bundle size in different builds.
-
-## Open Graph
-
-Open Graph tab is to help you with SEO, it shows you a Social Preview Card for twitter, facebook and linkedIn for your page. It also provides missing SEO tags with the ability to copy code snippets.
-
-## Plugins
-
-Plugins tab shows all the plugins your project is using, with some information such as plugin's initialization time.
-
-## Server Routes
-
-Server Routes tab shows all nitro routes in your project. It provides a playground to send and test your endpoints.
-
-## Storage
-
-Storage tab shows all the nitro storage in your project. You can create, edit, and delete files.
-
-Learn more about [Nitro Storage](https://nitro.unjs.io/guide/storage)
-
-## Tasks
-
-Tasks tab shows all nitro tasks in your project. You can pass task payloads, run them, and see the task results.
-
-Learn more about [Nitro Tasks](https://nitro.build/guide/tasks)
-
-## Data Inspector
-
-The **Data Inspector** lives in the Nuxt group and is an interactive [jora](https://discoveryjs.github.io/jora/) query workbench over your live server-side configuration. It replaces the old read-only Nuxt Options Viewer.
-
-Its `Nuxt Application` source exposes three root fields:
-
-- `nuxt` β the resolved Nuxt options.
-- `nitro` β the resolved Nitro options (populated once Nitro is created).
-- `vite` β the resolved Vite `client` and `ssr` environment configs.
-
-The source is live: every query reads the current state, so re-running a query after the Nitro/Vite hooks have completed reflects the latest values. Four read-only presets are provided β **Overview** (the whole object), **Nuxt options**, **Nitro options**, and **Vite configs** β each with function exclusion enabled so browsing configuration does not foreground methods. Your own custom queries are unrestricted and can invoke reachable functions or getters.
-
-The panel's bundled UI includes an optional polling toggle (5s default, clamped 1β3600s) that pauses in background tabs.
-
-Module authors who want to expose their own data can install [`@devframes/plugin-data-inspector`](https://npmx.dev/package/@devframes/plugin-data-inspector) and register sources through its `registerDataSource` API; they appear in the same inspector without any Nuxt-specific wrapper.
-
-::warning
-The `getServerData` DevTools RPC that backed the old viewer is deprecated (`NDT_DEP_0009`). It still works as a compatibility shim but will be removed; use the Data Inspector panel instead.
-::
-
-## Code Server
-
-The **Code Server** member in the Nuxt group embeds [Coder's `code-server`](https://coder.com/docs/code-server/install). It is enabled by default: Nuxt DevTools detects the local `code-server` binary during setup, but starts no process until you choose **Launch editor**. If the binary is missing, the member shows installation instructions instead.
-
-When launched, Code Server opens the Nuxt root directory by default, hands the generated authenticated session to the iframe, and streams process output to the built-in **Terminals** member. The process is also stopped when Nuxt closes.
-
-```ts [nuxt.config.ts]
-export default defineNuxtConfig({
- devtools: {
- codeServer: {
- enabled: true,
- // All fields below are optional.
- bin: '/usr/local/bin/code-server',
- cwd: '/workspace/my-app',
- serverPort: 8080,
- host: '127.0.0.1',
- args: ['--disable-file-downloads'],
- env: { LOG_LEVEL: 'info' },
- cookieSuffix: 'my-app',
- startTimeout: 30_000,
- },
- },
-})
-```
-
-The curated options are `enabled`, `bin`, `cwd`, `serverPort`, `host`, `args`, `env`, `cookieSuffix`, and `startTimeout`. When omitted, the upstream plugin defaults apply: the `code-server` binary, loopback host, a free port near Code Server's port 8080, and a 30-second startup timeout. Nuxt changes only the default `cwd`, setting it to the Nuxt root. Set `codeServer.enabled: false` to omit the member.
-
-Nuxt DevTools owns authentication, so `args` cannot override `--auth`, `--bind-addr`, or `--cookie-suffix`, and `env` cannot set `PASSWORD` or `HASHED_PASSWORD`. Configure the bind host and cookie suffix through their dedicated fields.
-
-The editor iframe connects directly to the Code Server port; Nuxt does not proxy it through `app.baseURL`. The browser must be able to reach that host and port, and an HTTPS page cannot embed an HTTP-only editor because of browser mixed-content rules. Binding to a non-loopback interface also exposes the port to that network, so apply the usual network controls.
-
-This integration uses the experimental upstream `@devframes/plugin-code-server`. HTTPS, reverse proxies, containers, and remote port forwarding are governed by that plugin and your environment; Nuxt does not extend them or provide the removed Microsoft/tunnel/reuse modes.
-
-## Hooks
-
-Hooks tab can help you to monitor the time spent in each hook. It can be helpful to find performance bottlenecks.
-
-
-
-## Virtual Files
-
-Virtual Files tab shows the virtual files generated by Nuxt to support the conventions.
-
-
-
-## Inspect
-
-Inspect expose the [`vite-plugin-inspect`](https://github.com/antfu/vite-plugin-inspect) integration, allowing you to inspect transformation steps of Vite.
-
-`vite-plugin-inspect` is an optional peer dependency, so it is not installed by default. Until you add it to your project, DevTools shows an install launcher in the Inspect slot (the same experience as Vite Plus DevTools) β click it to install the plugin and restart the dev server to activate the view.
-
-
-
-## Settings
-
-Settings tab allows you to configure the DevTools to your needs. you can hide tabs, change tabs order, scale, theme and more...
diff --git a/docs/content/1.guide/2.composables.md b/docs/content/1.guide/2.composables.md
deleted file mode 100644
index c0eb96037f..0000000000
--- a/docs/content/1.guide/2.composables.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Composables
-description: Open or control Nuxt DevTools with the useNuxtDevtools composable.
----
-
-In case you might want to open or control the Nuxt DevTools in your application on development, a composable `useNuxtDevtools` is registered with auto-import.
-
-```vue
-
-
-
-
-
-```
-
-When you have auto-import disabled, you can also import it explicitly:
-
-```ts
-import { useNuxtDevTools } from '#imports'
-```
-
-Checkout it's type definition for more available methods.
diff --git a/docs/content/3.development/0.contributing.md b/docs/content/3.development/0.contributing.md
deleted file mode 100644
index 2f48b031db..0000000000
--- a/docs/content/3.development/0.contributing.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Contribution Guide
-description: 'Learn how to contribute to the Nuxt DevTools.'
----
-
-Hi! We're really excited that you're interested in contributing to Nuxt DevTools! Before submitting your contribution, please read through the following guide.
-
-## Monorepo
-
-The Nuxt DevTools repo is a monorepo using pnpm workspaces. The package manager used to install and link dependencies must be [pnpm](https://pnpm.io/).
-
-After cloning the repo, run in the root folder.
-
-```sh
-pnpm i
-pnpm run build
-```
-
-::callout
-Nuxt DevTools uses pnpm v12. If you are working on multiple projects with different versions of pnpm, it's recommended to enable [Corepack](https://github.com/nodejs/corepack) by running `corepack enable`.
-::
-
-## Packages
-
-This repo contains the following packages:
-
-- `@nuxt/devtools`: The Nuxt DevTools module
-- `@nuxt/devtools-ui-kit`: The UI Kit used by Nuxt DevTools and also for module authors to build UI for DevTools interation
-
-### DevTools
-
-Most of the scripts are forward to the root `package.json`. You can run `pnpm dev` in the root folder to start the development server (Nuxt DevTools on top of it's own client UI).
-
-Or you can `cd packages/devtools` and run `pnpm dev` to start the development server.
-
-### UI Kit
-
-Normally when you are developing the Nuxt DevTools, the components in the UI Kit already get the HMR capabilities. But if you want to develop the UI Kit itself, you can run `cd packages/devtools-ui-kit` and run `pnpm dev` to start the playground for the UI Kit.
-
-## Trying Local Changes
-
-If you want to try your local changes in other Nuxt projects, you can use the `local.ts` module under the root folder.
-
-Change `@nuxt/devtools` to the absolute path of this module in any of your Nuxt projects,
-allows you to try Nuxt DevTools locally directly from the source code. HMR is supported
-for the front-end client.
-
-For example, if you clone this repo to `/users/me/nuxt-devtools`, update your `nuxt.config.ts`:
-
-```diff [nuxt.config.ts]
-export default defineNuxtConfig({
- modules: [
-- '@nuxt/devtools',
-+ '/users/me/nuxt-devtools/local',
- ]
-})
-```
-
-On the module code, the source TypeScript file are directly used, so you don't need to build everytime. However, due to Node.js module caching, you need to restart your app to see the changes on the module side.
diff --git a/docs/content/home/get-started.md b/docs/content/home/get-started.md
deleted file mode 100644
index 0df4f8dd90..0000000000
--- a/docs/content/home/get-started.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-navigation: false
----
-
-You just need to go to your `nuxt.config` file and set `devtools` to `true`:
-
-```ts [nuxt.config.ts]
-export default defineNuxtConfig({
- devtools: { enabled: true },
-})
-```
-
-Nuxt will automatically install the DevTools module for you.
diff --git a/docs/content/index.yml b/docs/content/index.yml
deleted file mode 100644
index 18bcd60662..0000000000
--- a/docs/content/index.yml
+++ /dev/null
@@ -1,53 +0,0 @@
-navigation: false
-hero:
- title: 'Unleash Nuxt -%}zb
ztb-(iva{_K@+4GwB5#b>Fo6E`QKgi#rKQm{GByXMm))5jS>68*5!s )g#`oO8rr~dy+#gmwp_902|A;{K(Ax9nP3SZh2PnRs5zfcp{#|V(o
zU8)7miuiamGtw(0lS@5Y09MW3WE30#q^xi__~E{Giz)vjJ?K%M-hN-aN$I|FjXBBa
zQdo_~v@I;kpF4VcF+2u)XU<`0N+&I8O3q{7=yJofw29ObI?U#)k}^F{gfFg&nOHIV
z`z$9O)5noE7OP+ULdb(`|8W>k?6c}ORV9r^ixiX*|C5YA`QX&nr9GY!+Jm|w#|)CF
z(OR26TA75e4E(^!R`->zw31(HPx70kLAPybSXmVk)~nk!Lf70SsS7)Z5WXB6r-#{i
z7Oj>%CmJrJuYceskW-Dqyl-oaG*P?B2@}d4Tt1@q(#bwvKFLBE(l1j4Nzgx3Rv`wM
zZGj9SKN(4^ke>!j{#bzegEX^6OF0eN+cj5Vt=l0eHeS{(KI1hxV{f87J5Al0du2{P
zbWR+Kwl#LOEdRs*UsNrp>pUWwqg3Ef4e{Z_)JRDpg*}&F;8~WV%{HXXdUf@PugAs*
zO-WUM5D^k-SsGHgp{gm{I`N$mf_vfb4PlIR0_PJ)hx2e|gZ~bPgjpx`vroaaT%OQ$
zvk7aVf;WAXaLD!&wJFnB`6(;j>h3`r+1Vqs1IFuW9Bjcj2E8mvb1Oz^?y8;8es>ht
z7QTPX>|84|C~n(xhVE0M$JCAw^n8dLl@1ahBBBO`^S{TR%QHR+FEy-+0R2yCsb*Zy
zD S0SoZL=Zu6o}+H5D7iSWxi_}&v>yP0g@2ptO;QR&tg3Q
zJ@S`Sfpk>