`nuxt doctor`
Open
Nobody has claimed this yet.
discussion
enhancement
- Dominant language
- TypeScript
- Stars
- 399
- Forks
- 119
- Avg merge
- 20h 59m
- Merged PRs (30d)
- 65
Description
would be handy to have a command to diagnose issues. It could include utilities to resolve package dependency issues, such as:
- outdated versions of unjs utils (defu, untyped)
https://github.com/nuxt/nuxt.js/issues/14768
https://github.com/nuxt/nuxt.js/issues/14538 - nuxt 2 modules in dep list (even if not in
nuxt.config)
https://github.com/nuxt/nuxt.js/issues/14945 - monorepo hoisting issues (though https://github.com/nuxt/nuxt.js/issues/11074 implementation should have dealt with some of this)
- mismatched (or multiple) versions of
vuedeps
https://github.com/nuxt/nuxt.js/issues/14952 - incorrect casing in nuxt folders (on a case-insensitive file system)
- https://github.com/nuxt/cli/issues/1448
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 reviewing the scope of the proposed nuxt doctor command and the linked Nuxt and Nuxt CLI issues. Identify which dependency, module, monorepo, Vue version, folder-casing, and related checks are still relevant. Done means the project has an agreed diagnostic scope and a clear way to verify each reported problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxtjs, typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100