nuxt / nuxt/devtools

Standalone nuxt devtools app

Open
#687 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
3.3k
Forks
214
Avg merge
13h 22m
Merged PRs (30d)
18

Description

🆒 Your use case

Would be great to have a standalone app (electron based) like vue-devtools-next.

Its a great experience to work on your app especially when we could have the devtools (which is super feature-rich) in a secondary monitor. Also, having the devtools opening up with the app itself can sometimes be hard to work with especially on a laptop screen.

Thanks for considering this. May be this could be part of potential convergence of the vue & nuxt devtools?

🆕 The solution you'd like

Standalone electron version of the nuxt-devtools.

🔍 Alternatives you've considered

Currently, Popup as Picture-in-Picture feature is useful but I notice that it's not very reliable in terms of connection https://github.com/nuxt/devtools/issues/690.

Also, in some environments such as working on an electron app or stackbliz, popup is not an option as it works only from the top level context. Please refer to the error logged in the console in below screenshot.

image

ℹ️ Additional info

https://stackblitz.com/github/TechAkayy/nuxt-devtools-popup?file=README.md

  • Browser - Chrome Version 126.0.6478.114 (Official Build) (arm64)
  • Operating System: Darwin
  • Node Version: v20.14.0
  • Nuxt Version: 3.12.3
  • CLI Version: 3.12.0
  • Nitro Version: 2.9.7
  • Package Manager: npm@10.7.0
  • Builder: -
  • User Config: devtools, modules
  • Runtime Modules: -
  • Build Modules: -

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the standalone Electron reference linked for vue-devtools-next and the current Popup as Picture-in-Picture approach described in this issue, including issue #690. Define the standalone app's integration and connection behavior; done means Nuxt DevTools can run reliably in its own Electron window, including environments where popup is unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, nuxt, typescript
Domain
desktop, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.