sneak
5b07c90933
check / check (push) Successful in 3m54s
script/lint ran prettier --check, the same check script/fmt-check runs, so the JavaScript had no linter. eslint now runs with its recommended rules, set in eslint.config.js, in a new frontend-lint stage of Dockerfile built from the pinned node image and the lockfile. The frontend stage copies a file from it, as the builder stage does from the Go lint stage, so the image cannot build unless eslint passed. script/lint builds both lint stages with --no-cache and runs no linter on the host; script/fmt-check keeps prettier on the host, and script/frontend-check drops its lint step. The viewport harness fixes the two kinds of finding eslint made. bootstrap wants node 22.13.0, as eslint 10 does. Also covers item 2 of #28. Model: opus-5-5
25 lines
623 B
JSON
25 lines
623 B
JSON
{
|
|
"name": "netwatch",
|
|
"version": "1.0.0",
|
|
"description": "Real-time network latency monitor SPA",
|
|
"type": "module",
|
|
"scripts": {
|
|
"dev": "vite",
|
|
"build": "vite build",
|
|
"preview": "vite preview"
|
|
},
|
|
"license": "MIT",
|
|
"devDependencies": {
|
|
"@eslint/js": "^10.0.1",
|
|
"@tailwindcss/vite": "^4.1.18",
|
|
"autoprefixer": "^10.4.23",
|
|
"eslint": "^10.12.0",
|
|
"globals": "^17.13.0",
|
|
"postcss": "^8.5.6",
|
|
"prettier": "^3.8.1",
|
|
"puppeteer-core": "25.5.0",
|
|
"tailwindcss": "^4.1.18",
|
|
"vite": "^7.3.1"
|
|
}
|
|
}
|