Revisit --no-type-check
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, rust
Research direction
Start at the vp check command and the vite.config.js#lint.typeCheck setting. Trace how command-line options override the current configuration, then verify that --no-type-check disables type checking while format and non-type-related lint checks still run.
Written by the indexing model from the issue text.
Description
Description
Hi, I'd made a comment here on the original issue for this request, but after it was closed.
My use case for the original proposition was to have a way to to use 'vp check' without type checking when I want to check files in isolation, for example, as a PostToolUse hook after an agent touches a file. My understanding is that unless the code base enforces isolatedDeclarations, the whole graph is required to type check, where all I want is to run the format and non-type related lint rules in that check. The goal is to save tokens by not having an agent run basic lint and format commands, and doing full type checking only when needed for verifying its task.
Suggested solution
Have a --no-type-check flag which sets vite.config.js#lint.typeCheck flag to false for the current execution.
Alternative
No response
Additional context
No response
Validations
- Read the Contributing Guidelines.
- Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
- Check that there isn't already an issue requesting the same feature.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 263
- Avg merge
- 22h 44m
- Merged PRs (30d)
- 134
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.
More from voidzero-dev/vite-plus
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
voidzero-dev/vite-plus#2097 · 10 comments · 2 reactions ·
-
bug enhancement
voidzero-dev/vite-plus#2746 · 3 comments · 1 reaction · 1 assignee ·
-
voidzero-dev/vite-plus#2728 · 1 comment · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
voidzero-dev/vite-plus#2703 · 1 assignee ·
-
enhancement pending triage
Difficulty 4/5 3-5 days Newbie friendliness 55/100
voidzero-dev/vite-plus#2698 · 10 comments · 1 reaction ·
All issues in voidzero-dev/vite-plus
Similar issues
-
risk:low runtime status:in-progress type:test
Difficulty 1/5 Under an hour Newbie friendliness 92/100
zeroclaw-labs/zeroclaw#11023 ·
-
good first issue refactor
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·