modelcontextprotocol/inspector
Watch
1
0
Fork
You've already forked inspector
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

chore: ignore the web client's tsup build output in ESLint

Browse source 
clients/web emits two bundles — dist (the Vite SPA) and build (the tsup
prod-server runner) — but only dist was in globalIgnores, so `npm run lint`
parsed ~1.2MB of generated output and reported an unused-eslint-disable
warning from inside the vendored undici source. Its three sibling clients
already ignore their build/ output.

Closes #2043

Signed-off-by: cliffhall <cliff@futurescale.com>
This commit is contained in:
cliffhall 2026-08-17 09:45:57 -04:00
commit 6b27e5f932
1 changed files with 6 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

7
clients/web/eslint.config.js
View file

@ -9,7 +9,12 @@ import tseslint from "typescript-eslint";
import { defineConfig, globalIgnores } from "eslint/config"; import { defineConfig, globalIgnores } from "eslint/config";
export default defineConfig([ export default defineConfig([
globalIgnores(["dist", "storybook-static", "coverage"]), // Generated output, none of it first-party source. Web is the only client
// that emits *two* bundles — `dist` (the Vite SPA) and `build` (the tsup
// prod-server runner, which vendors ~1.2MB of `undici`) — and only the first
// was originally listed, so `lint` reported a warning from inside undici's
// own source that nobody could act on (#2043).
globalIgnores(["build", "dist", "storybook-static", "coverage"]),
{ {
files: ["**/*.{ts,tsx}"], files: ["**/*.{ts,tsx}"],
extends: [ extends: [