svelte-check sits in devDependencies at ^4.7.3 and nothing in the repository ever invoked it, so the type errors it reports had no path to a human. Point a script at it and run it in the frontend job, and it is clean: 0 errors, 0 warnings. It shares the one `npm ci` with the test step. A second install would have doubled the slowest part of the job to learn exactly the same thing. The lockfile is untouched, because scripts are not part of what it pins. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
28 lines
651 B
JSON
28 lines
651 B
JSON
{
|
|
"name": "userbot-panel",
|
|
"private": true,
|
|
"version": "1.0.0",
|
|
"type": "module",
|
|
"scripts": {
|
|
"build": "vite build",
|
|
"dev": "vite --host 0.0.0.0",
|
|
"test": "vitest run",
|
|
"check": "svelte-check --tsconfig ./tsconfig.json"
|
|
},
|
|
"dependencies": {
|
|
"lucide-svelte": "^0.468.0",
|
|
"svelte": "^5.16.0"
|
|
},
|
|
"devDependencies": {
|
|
"@sveltejs/vite-plugin-svelte": "^5.0.0",
|
|
"@testing-library/jest-dom": "^6.6.3",
|
|
"@testing-library/svelte": "^5.2.6",
|
|
"@types/node": "^22.10.5",
|
|
"jsdom": "^25.0.1",
|
|
"svelte-check": "^4.7.3",
|
|
"typescript": "~5.7.2",
|
|
"vite": "^6.0.7",
|
|
"vitest": "^2.1.8"
|
|
}
|
|
}
|