Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

vp check --no-lint still reports type-aware lint rules and ignores their disable comments

Geschlossen
  • Stimmt etwas nicht?
#2,830 1 Kommentar 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@camc314 arbeitet bereits daran.

Seit 26.9.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

Describe the bug

vp check --no-lint is documented as "Skip lint rules; type-check still runs when lint.options.typeCheck is true". With typeAware and typeCheck enabled, though, it still reports type-aware lint rules, and it ignores their oxlint-disable comments. Plain vp check and vp lint both respect the comment, so the --no-lint run is the only one that fails.

Expected: --no-lint reports TypeScript diagnostics only.
Actual: type-aware rule diagnostics are reported (as errors), and disable directives have no effect.

I found this while moving a project to Vite+ 1.0.0-rc.1. The workaround is vp check --no-fmt, which runs the full lint as well.

Reproduction

Inline below, no repository needed.

Steps to reproduce
mkdir vp-no-lint && cd vp-no-lint && git init -q && mkdir src
printf 'node_modules\n' > .gitignore
cat > package.json <<'EOF'
{ "private": true, "type": "module",
  "devDependencies": { "typescript": "6.0.3", "vite-plus": "1.0.0-rc.1" } }
EOF
cat > tsconfig.json <<'EOF'
{ "compilerOptions": { "strict": true, "module": "esnext", "moduleResolution": "bundler", "target": "esnext" }, "include": ["src"] }
EOF
cat > vite.config.ts <<'EOF'
import { defineConfig } from "vite-plus";

export default defineConfig({
  lint: {
    options: { typeAware: true, typeCheck: true },
    rules: { "typescript/no-floating-promises": "error" },
  },
});
EOF
cat > src/index.ts <<'EOF'
// oxlint-disable-next-line typescript/no-floating-promises -- fire and forget
Promise.resolve();
EOF
vp install
vp check --no-fmt             # pass, exit 0
vp check --no-fmt --no-lint   # fails, exit 1

$ vp check --no-fmt
pass: Found no warnings, lint errors, or type errors in 2 files (270ms, 8 threads)

$ vp check --no-fmt --no-lint
error: Type errors found
x typescript(no-floating-promises): Promises must be awaited, add void operator to ignore.
   ,-[src/index.ts:2:1]
 1 | // oxlint-disable-next-line typescript/no-floating-promises -- fire and forget
 2 | Promise.resolve();
   : ^^^^^^^^|^^^^^^^^^
   :         `-- This unhandled promise-like value has type `Promise<void>`.
   `----

Found 1 error and 0 warnings in 2 files (273ms, 8 threads)

This does not look like an Oxlint bug. Running vp lint -A all --type-aware --type-check on the same project reports nothing, and a real type error (const n: number = "x") is reported correctly by vp check --no-lint, next to the rule diagnostic above.

System Info
$ vp --version
vp v1.0.0-rc.1

Local vite-plus:
  vite-plus  v1.0.0-rc.1

Tools:
  vite             v8.3.1
  rolldown         v1.2.11
  vitest           v5.0.1
  oxfmt            v0.70.0
  oxlint           v1.85.0
  oxlint-tsgolint  v7.0.2003
  tsdown           v0.23.0

$ vp env current
Node.js:
  Version    26.10.0
  Source     system PATH
  Mode       system_first

Package Manager:
  Name       pnpm
  Version    12.6.0
  Source     system PATH
  Mode       system_first

macOS (arm64).

Used Package Manager

pnpm

Validations
  • Read the Contributing Guidelines.
  • Checked that there isn't already an issue for the same bug.
  • Confirmed this is a Vite+ issue and not an upstream issue (Oxlint alone behaves correctly, see above).
  • The reproduction is a minimal reproducible example.
Vorherrschende Sprache
Rust
Sterne
6.5k
Forks
296
Ø Merge
1 T. 5 Std.
Gemergte PRs (30 T.)
224

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus voidzero-dev/vite-plus

Alle Issues in voidzero-dev/vite-plus

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.