Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
support for unit testing in a nuxt environment
See original GitHub issueDescribe the feature
Unit testing (e.g. [parts of ]composables or server functions) doesn’t require a full built of nuxt.
_Originally posted by @pi0 in https://github.com/vitest-dev/vitest/issues/2044#issuecomment-1251939691_
We plan to support also unit testing with
nuxi testbut properly in a Nuxt environment. Exposing vite config only is not enough for doing that and in past similar approach made lots of headaches for testing in Nuxt 2. However, probably will expose as a@nuxt/kitutility anyway as an alternative to current usage that needs replicating vite config for aliases.
Related: https://github.com/nuxt/framework/issues/2465 (auto-import issues when testing components)
issue description from https://github.com/nuxt/framework/issues/7672 - @tobiasdiez
Issue Analytics
- State:
- Created 2 years ago
- Reactions:21
- Comments:25 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
For those who can’t see the status, I’m working on this issue at the moment - which I think is pretty important. Here’s a spoiler: https://twitter.com/danielcroe/status/1590490011501142017.
Just wanting to add that this is quite a crucial feature to have, because right now we can’t run component tests in nuxt3.
Vitest also doesn’t know about the magic auto-imports, so I think it would be nice if Nuxt3 exposed a method that we can call in vitest for this.
Edit: I’ve found that the
unplugin-auto-importplugin works well with providing its own vite config to vitest.