fix(frontend): sync package-lock.json with lucide-react (P0 deploy fail) #345
No reviewers
Labels
No labels
admin
analytics
auth
automation
bug
business
chore
ci
compliance
data
data-moat
docs
duplicate
dx
enhancement
Fable 5 ревью
feedback/max
generative
GG-форсайт
needs-discussion
needs-human
observability
pause-bots
performance
priority/p0
priority/p1
priority/p2
priority/p3
scope/backend
scope/db
scope/devops
scope/frontend
scope/qa
scrapers
security
site-finder
stage/1
stage/2
status/blocked
status/done
status/needs-analysis
status/needs-fix
status/qa
status/ready
status/review
status/wip
tech-debt
tradein
ux
week ревью 1
wontfix
вторичка
ИРД
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lekss361/gendesign#345
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "fix/frontend-lucide-react-lockfile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
P0 hotfix — deploy #135 fail on main:
Root cause
A4 PR #344 добавил
lucide-react ^0.511.0вfrontend/package.jsonно worker не запустилnpm install→package-lock.jsonне sync'нут →npm ci(требует lockfile match) падает → frontend Dockerfile builder step fails → весь deploy aborts (uses--abort-on-container-exit).A1 #340 уже импортировал
lucide-reactв shell (без deps entry — был slip), A4 добавил dep но не lockfile.Fix
Локальный
npm install --legacy-peer-depsregen sync'нул lockfile:node_modules/lucide-react@0.511.0entryVerify
npm run buildлокально — все 18 routes compile clean./site-finder7.57 kB,/site-finder/analysis/[cad]4.19 kB.Closes deploy #135 fail.
Deep Code Review — verdict APPROVE
Summary
frontend/package-lock.jsononly)Verification
lucide-react@0.511.0entry present in lockfile root deps (line 14) +node_modules/lucide-reactentry with correct registry URLhttps://registry.npmjs.org/lucide-react/-/lucide-react-0.511.0.tgzand peerDepreact ^19✅@webassemblyjs/*,terser,terser-webpack-plugin,webpack,webpack-sources,watchpack,schema-utils,ajv-formats,jest-worker, etc.) — all flagged"peer": truein old lockfile, never referenced from direct deps. Next.js 15 bundles its own SWC compiler, doesn't pull webpack into resolved tree.@types/json-schema,enhanced-resolve,esrecurse,estraverse,graceful-fs,json-schema-traverse,tapable,require-from-string) kept in lockfile — only had"dev": trueflag added (correct: devDeps-only now).next@15.5.15,react,react-dom,tailwindcss@4.2.4,@tanstack/react-query,leaflet,leaflet-draw,echarts— none deleted.package.jsonchanges (A4 #344 already had the dep).Cross-file impact
npm cion deploy will now succeed: lockfile satisfies allpackage.jsondependencies.Positive observations
npm install --legacy-peer-depswas the right tool (echarts/leaflet peer mismatch with React 19)Merging now to unblock prod deploy.