You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7937843
Browse filesBrowse the repository at this point in the historyBrowse files
Use Vite+'s tsrs checker with explicit compiler settings and local project
configs, including previously unchecked tests and the build agent. Fix type
contracts, update mocks, await asynchronous test cleanup, and keep deliberate
background work explicit. Update CI and contributor commands; retain compiler
compatibility checks for ignored/generated files and TypeScript 6 consumers.
Validation: 822 test files / 17,550 tests passed (35 skipped), 35 Node tooling
tests passed, workspace and docs builds passed, compiler checks passed, and
six deliberately injected type errors were detected by the final config.
Apple M4 Pro, Node 24.22.1, shared installed dependencies and prepared
build outputs, one warm-up and five alternating measured runs per command:
- Original vpr check median: 5.204s
- New vp check median: 3.455s
- 33.6% less time (1.51x speedup), with formatting and lint included.
Copy file name to clipboardExpand all lines: AGENTS.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Deploy hosted production before publishing the npm packages: the CLI checks the
24
24
- Every implementation plan should include the following:
25
25
- During plan generation: ask clarifying questions when necessary, especially around developer-experience defining design decisions.
26
26
- Verification:
27
-
- Run `vp run check` for package typechecking after completing a batch of tasks.
27
+
- Run `vp check` for formatting, linting, and workspace typechecking after completing a batch of tasks.
28
28
- During development, run an exact test file (and `-t` for a focused case) first. Use `vp run test --list` to inspect affected coverage, then `vp run test` for changed-file validation. Use `--base <ref>` when changes are already committed; the default includes only staged, unstaged, and untracked files.
29
29
-`vp run test --unit` is an iteration-only shortcut, not integration verification. Native `vp test related --run <source>` misses filesystem/subprocess inputs; prefer the smart runner's conservative fallbacks before handing off. See `TESTING.md` for builds, integration selection, and import profiling.
30
30
- Run `vp test run` once when everything is done for final verification. CI and `vpr test:all` retain full-suite coverage. Do not repeatedly run the full suite during iteration, enable result caching for the smart selector, or disable module isolation to make tests faster.
@@ -54,7 +54,7 @@ vpr test:all # Format, lint, build, typecheck, and run al
54
54
vp test run packages/void # Only test the core plugin
55
55
vp lint # Oxlint through Vite+
56
56
vp fmt # Oxfmt through Vite+
57
-
vp run check # Typecheck all packages with TypeScript
57
+
vp check # Format, lint, and typecheck the workspace
58
58
vp run --filter ./packages/vue typecheck # Typecheck a specific package
0 commit comments