aarbitandClaude Sonnet 5
71e4c2c22d
The last pipeline run failed on \`npx wrangler deploy\` with npm unable to find wrangler@4.144.0 — a transient registry propagation gap right after that version's release, not an actual config problem (it installs fine moments later, confirmed locally). Both wrangler and the supabase CLI were being fetched fresh via bare npx on every single pipeline run instead of coming from the lockfile like every other dependency, which is exactly what left CI exposed to whatever npm's registry happens to be doing at that moment. Pinning them means npm ci resolves the exact locked version every time, and npx picks up the local install instead of hitting the registry at all. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017DUU6CnxECCDeqDNYJgr5x
38 lines
965 B
JSON
38 lines
965 B
JSON
{
|
|
"name": "av-planner",
|
|
"private": true,
|
|
"version": "0.0.0",
|
|
"type": "module",
|
|
"scripts": {
|
|
"dev": "vite",
|
|
"dev:lan": "vite --host",
|
|
"build": "tsc -b && vite build",
|
|
"lint": "oxlint",
|
|
"preview": "vite preview",
|
|
"export-seed": "node scripts/export-seed.mjs",
|
|
"db:reset": "node scripts/export-seed.mjs --check && npx supabase db reset"
|
|
},
|
|
"dependencies": {
|
|
"@supabase/supabase-js": "^2.115.0",
|
|
"@xyflow/react": "^12.11.5",
|
|
"react": "^19.2.8",
|
|
"react-dom": "^19.2.8",
|
|
"uuid": "^14.0.2",
|
|
"zustand": "^5.0.15"
|
|
},
|
|
"devDependencies": {
|
|
"@tailwindcss/vite": "^4.3.3",
|
|
"@types/node": "^24.13.3",
|
|
"@types/react": "^19.2.18",
|
|
"@types/react-dom": "^19.2.4",
|
|
"@types/uuid": "^10.0.0",
|
|
"@vitejs/plugin-react": "^6.1.0",
|
|
"oxlint": "^1.79.0",
|
|
"supabase": "^2.118.0",
|
|
"tailwindcss": "^4.3.3",
|
|
"typescript": "~6.0.2",
|
|
"vite": "^8.2.2",
|
|
"wrangler": "^4.143.1"
|
|
}
|
|
}
|