Handling nuxi testing errors
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 399
- Forks
- 119
- Avg merge
- 20h 59m
- Merged PRs (30d)
- 65
Description
Using nuxi testing without having testing packages installed causes the following behavior
There are multiple points about it:
- Along with
Vitest, It asks for@nuxt/test-utilsor@nuxt/test-utils-edge. can it be limited to guide users towards the stable package ? - Can we handle installing these packages with a Yes/No question ?
- I also suggest offering direct installation for Vitest module.
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 with the nuxi testing command and reproduce its behavior when Vitest, @nuxt/test-utils, and @nuxt/test-utils-edge are absent. Done means the command guides users toward the stable package, asks before installing testing packages, and offers direct installation of the Vitest module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxtjs, typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100