work-board: regenerate package-lock with npm 10 to match node:22 CI (fix npm ci drift)

Browse Source

The @luxfi/[email protected] migration regenerated the lock with npm 11, which dedupes the
[email protected] that @luxfi/ui's @expo/* deps require — but the Dockerfile builds on
node:22-alpine (npm 10) via 'npm ci', which demands those nested entries and failed
EUSAGE 'Missing: [email protected] from lock file'. Regenerate the lock with npm 10 so it
matches the build tool; no bypass of npm ci.

Co-authored-by: Hanzo Dev <[email protected]>

...

This commit is contained in:

zeekay

2026-07-18 23:48:58 -07:00

co-authored by Hanzo Dev

parent c04b747f23

commit f0f4a4d6ca

1 changed files with 91 additions and 1050 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

package-lock.json

Generated

+91 -1050

File diff suppressed because it is too large Load Diff