Repository navigation
command vp check -h lists the non existing example flag --no-type-check #964
Description
Describe the bug
The help output looks like the following:
$> vp check -h
VITE+ - The Unified Toolchain for the Web
Usage: vp check [OPTIONS] [PATHS]...
Run format, lint, and type checks.
Options:
--fix Auto-fix format and lint issues
--no-fmt Skip format check
--no-lint Skip lint check
-h, --help Print help
Examples:
vp check
vp check --fix
vp check --no-type-check src/index.ts
Documentation: https://viteplus.dev/guide/checkUnder Examples the flag --no-type-check is shown, but it does not exist:
$> vp check --no-type-check app/app.vue
VITE+ - The Unified Toolchain for the Web
error: Unexpected argument '--no-type-check'Reproduction
https://github.com/voidzero-dev/vite-plus/
Steps to reproduce
- Open terminal.
- Verify with
vp check -hthat the example with flag--no-type-checkis listed. - Use
vp checkon any file or folder with flag--no-type-check, e.g.vp check --no-type-check app/app.vueinside a Nuxt v4 application.
System Info
$> pnpm -v
10.32.1
$> vp env current
VITE+ - The Unified Toolchain for the Web
Environment:
Version 24.14.0
Source lts
Tool Paths:
node /home/toddeTV/.vite-plus/js_runtime/node/24.14.0/bin/node
npm /home/toddeTV/.vite-plus/js_runtime/node/24.14.0/bin/npm
npx /home/toddeTV/.vite-plus/js_runtime/node/24.14.0/bin/npx
$> vp --version
VITE+ - The Unified Toolchain for the Web
vp v0.1.11
Local vite-plus:
vite-plus v0.1.11
Tools:
vite v8.0.0
rolldown v1.0.0-rc.9
vitest v4.1.0
oxfmt v0.40.0
oxlint v1.55.0
oxlint-tsgolint v0.16.0
tsdown v0.21.2Used Package Manager
pnpm
Logs
Validations
- Read the Contributing Guidelines.
- Check that there isn't already an issue for the same bug.
- Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
- The provided reproduction is a minimal reproducible example.
Activity
fengmk2 commentedon Mar 16, 2026
Fixed in v0.11.12 #875
you can upgrade vp by
vp upgradeand try again.toddeTV commentedon Mar 16, 2026
I can confirm, this was fixed in #875 and does not occur anymore.
Good job and thanks :)
toddeTV commentedon Mar 16, 2026
Just for logging: