nuxt / nuxt/devtools

DevTools UI improvement

Open
#430 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

while developing modules for DevTools, It feels like some components are missing or some can be refactored to have more features. here is a list:

  • NTable: unavailable
  • NPagination: unavailable
  • NTabs: unavailable
  • NDialog or NModal: we have Dialog component in @nuxt/devtools, we can refactor and move it to ui.
  • NDrawer: we have DrawerRight & DrawerBottom component in @nuxt/devtools, we can refactor and move it to ui.
  • NNotification: we have Notification component in nuxt-devtools, we can refactor and move it to ui.
  • NNavbar: we have Navbar component in @nuxt/devtools, we can refactor and move it to ui because it's often use.
  • NSplitPane: we have PanelLeftRight component in @nuxt/devtools, we can refactor and move it to ui.
  • NTooltip: we are using floating-vue for tooltips too in @nuxt/devtools, but I think we can add tooltip with only css
  • NCommandPalette: we have CommandPalette component in @nuxt/devtools, we can refactor and move it to ui
  • NAlert: there is already NTip but I think NAlert is more common for use
  • NBadge: we have Badge component in @nuxt/devtools, we can refactor and move it to ui
  • NLink & NTextExternalLink: can refactored to one component
  • NButton & NIconButton: can refactored to one component (with support for group-buttons)

also there is this thought that maybe user wants to use @nuxt/devtools-ui for any other project so it would be neat if we add some other components too (e.g. NAvatar, NProgress ...)

If there are any additional components or improvements that have been overlooked, please feel free to add them to the list. let me know what you think, thanks

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 existing components in @nuxt/devtools and the target @nuxt/devtools-ui package, focusing on the unchecked items in the list. Determine which components are actually required and whether the requested refactors share a settled design. Done means the scope is agreed and the selected components or refactors are implemented consistently in the UI package.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience, frontend, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.