Add plugin package name
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 89
- Avg merge
- 18h 46m
- Merged PRs (30d)
- 24
Description
Clear and concise description of the problem
Currently, it is not obvious which plugin originated from which package. It would be helpful to show that information.
Suggested solution
Recommend plugins to add api.devtools.package values:
const p = {
name: 'foo',
api: {
devtools: {
package: '@vitejs/plugin-vue'
}
}
}
and make devtools will read that information.
We can also add description property to show it.
Alternative
No response
Additional context
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guide.
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the code that reads plugin metadata and renders recommended plugins in the Vite devtools repository. Trace how the proposed api.devtools.package value could reach that display, then identify the relevant tests or UI coverage. Done means the originating package is shown consistently, with any added description behavior clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vite
- Domain
- devtools, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100