Context
When users hit issues with the CLI, the first question is usually "what does your env look like?" — node version, network access, registry reachable, package versions, etc. A doctor command surfaces all of this in one place and gives users something concrete to paste into bug reports.
What to build
Implement w3-kit doctor that runs a battery of checks and prints a readable report:
- Node version (and whether it meets the supported range)
- npm/pnpm/bun version
- OS / arch
- Network: can the CLI reach the registry source / GitHub / npm?
- Installed
@w3-kit/* package versions in the current project (if any)
- Any obvious config problems
Each check should be a single ✓ or ✗ line with an inline explanation when it fails.
Acceptance criteria
Pointers
Complexity
🟡 Intermediate
Context
When users hit issues with the CLI, the first question is usually "what does your env look like?" — node version, network access, registry reachable, package versions, etc. A
doctorcommand surfaces all of this in one place and gives users something concrete to paste into bug reports.What to build
Implement
w3-kit doctorthat runs a battery of checks and prints a readable report:@w3-kit/*package versions in the current project (if any)Each check should be a single
✓or✗line with an inline explanation when it fails.Acceptance criteria
w3-kit doctorruns all checks without crashing even if some fail--jsonflag (see related issue) also works here, returning a structured reportPointers
--jsonflagComplexity
🟡 Intermediate