Unleash Nuxt Developer Experience.
Nuxt DevTools is a set of visual tools that help you to know your app better.

👋 Introduction | 💡 Ideas & Suggestions | 🗺️ Project Roadmap | 📚 Documentation

Nuxt DevTools v2 requires Nuxt v3.15.0 or higher.

Nuxt DevTools is enabled by default in Nuxt v3.8.0. You can press Shift + Alt / ⇧ Shift + ⌥ Option + D in your app to open it up.

If you want to explicitly enable or disable Nuxt DevTools, you can update your nuxt.config with:

export default defineNuxtConfig({
  devtools: {
    enabled: true // or false to disable
  }
})

Nuxt DevTools v4.0 is currently in alpha. Since Nuxt ships with a built-in version of DevTools, you can opt-in to v4.0 by using package manager resolutions to override the bundled version:

{
  "overrides": {
    "@nuxt/devtools": "npm:@nuxt/devtools-nightly@latest"
  }
}

{
  "resolutions": {
    "@nuxt/devtools": "npm:@nuxt/devtools-nightly@latest"
  }
}

{
  "pnpm": {
    "overrides": {
      "@nuxt/devtools": "npm:@nuxt/devtools-nightly@latest"
    }
  }
}

Remove lockfile (package-lock.json, yarn.lock, or pnpm-lock.yaml) and reinstall dependencies.

Similar to Nuxt's Nightly Channel, DevTools also offers a nightly release channel, that automatically releases for every commit to main branch.

You can opt-in to the nightly release channel by using package manager resolutions:

{
  "overrides": {
    "@nuxt/devtools": "npm:@nuxt/devtools-nightly@latest"
  }
}

{
  "resolutions": {
    "@nuxt/devtools": "npm:@nuxt/devtools-nightly@latest"
  }
}

{
  "pnpm": {
    "overrides": {
      "@nuxt/devtools": "npm:@nuxt/devtools-nightly@latest"
    }
  }
}

Remove lockfile (package-lock.json, yarn.lock, or pnpm-lock.yaml) and reinstall dependencies.

To configure Nuxt DevTools, you can pass the devtools options.

// nuxt.config.ts
export default defineNuxtConfig({
  devtools: {
    // Enable devtools (default: true)
    enabled: true,
    // Coder code-server options (enabled by default)
    codeServer: {},
    // ...other options
  }
})

For all options available, please refer to TSDocs in your IDE, or the type definition file.

Read the Announcement Blog Post 🎊 for why we built Nuxt DevTools and what it can do!

Please refer to the Module Authors Guide.

Please refer to the Contribution Guide.

Nuxt DevTools collects anonymous telemetry data about general usage. This helps us to accurately gauge feature usage and customization across all our users. This data will let us better understand how each features in Nuxt DevTools are used, measuring improvements made (DX and performances) and their relevance. It would also help us to prioritize our efforts and focus on the features that matter the most to our users.

Nuxt DevTools' telemetry data is piped through Nuxt Telemetry, meaning that Nuxt DevTools will respect your local and global Nuxt Telemetry settings. You can also opt-out Nuxt DevTools' telemetry in the Nuxt DevTools settings.

Nuxt DevTools also respects the DO_NOT_TRACK environment variable convention — set DO_NOT_TRACK=1 in your environment to disable Nuxt DevTools telemetry regardless of any other setting.

The data we collect is completely anonymous, not traceable to the source (using hash+seed), and only meaningful in aggregate form. No data we collect is personally identifiable or trackable.

On top of the default Nuxt Telemetry events, Nuxt DevTools also collects the following events:

• Versions of Nuxt DevTools
• Navigations between tabs/feature
  • This helps us to understand which features are used the most to prioritize our efforts.
• Browser and OS names and versions
  • This helps us improve compatibility across different browsers and operating systems.
• Click event on some action buttons

MIT