Remove vitest global types to encourage vitest imports and prevent misconfig errors #152
Labels
bug
Something isn't working
good first issue
Good for newcomers
help wanted
Extra attention is needed
Package: Coding Standards
Issues related to the Coding Standards package
Our vitest typescript config currently loads vitest functions as global variables, which means they don't throw and error if they aren't imported.
To fix this issue, we should remove global import types and require vitest consumers to import their functions explicitly.
The text was updated successfully, but these errors were encountered: