Comments (3)
Thanks the reproduction. It looks like a bug to me. Probably --typecheck
flag is somehow consuming the next argument (though I'm not sure how it's meant to work currently). I found --api
flag also does something similar, which might also need to be adjusted:
vitest/packages/vitest/src/node/cli.ts
Lines 63 to 65 in 6421c27
vitest/packages/vitest/src/node/cli.ts
Line 23 in 6421c27
from vitest.
Not ideal but to workaround this issue, using --typecheck.enabled
instead of --typecheck
should achieve what you're probably intending to do.
Also, setting typecheck: { enabled: true }
is also possible if you want to enable type-checking for any vitest
run.
from vitest.
Not ideal but to workaround this issue, using
--typecheck.enabled
instead of--typecheck
should achieve what you're probably intending to do. Also, settingtypecheck: { enabled: true }
is also possible if you want to enable type-checking for anyvitest
run.
Thanks!
I resolved it by the setting the config option, but still wanted to report the issue.
from vitest.
Related Issues (20)
- The method "toHaveBeenCalledTimes" is not counting mock calls in a map with an async function, when there is at least 2 different functions HOT 2
- Documentation includes unsupported flags
- `ignoreSourceErrors` is ignored when `run`ning typecheck
- No way to identify "thread" when using pool=forks HOT 6
- Method getUnhandledErrors called on RPC, but does not exist and throws error HOT 6
- ReferenceError: process is not defined when using vi.useFakeTimers in browser mode
- Tests are duplicated after hitting "u" in watch mode to update snapshots HOT 2
- vite+ts+vitest,安装了echarts,jsdom,测试echarts.setOption会失败退出进程,没有任何报错提示 HOT 7
- v8 coverage provider report 100% statement coverage for uncovered v-if inside template HOT 6
- network imports not working on `vmThreads` and `vmForks` pools
- Rerun on save not covering other test files HOT 14
- Typecheck checking types in files not related to test files HOT 3
- Preact + @tanstack/react-query returns TypeError: Cannot read properties of null (reading 'useEffect') HOT 3
- `vitest related` with barrel files HOT 1
- `import.meta.filename` and `import.meta.dirname` is `undefined` on Node.js Latest LTS `v20.11.0`
- json-summary output messed json file when use shard argument to split test task HOT 2
- Coverage Report Path in Browser Mode Does Not Consider "reportsDirectory" HOT 10
- `viteOverrides` option in `startVitest` doesn't affect browser mode config HOT 2
- `test.env` config not working in workspace project HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vitest.