chore(frontend): normalize package-lock.json ordering via npm

Browse Source

This commit contains zero hand edits. Running `npm install` in a fresh
worktree rewrites package-lock.json into npm's canonical form, which
produces ~8.6k changed lines of pure noise:

- all 961 `packages` keys re-sorted into npm's lexicographic order
  (945 were previously out of spec order)
- 6 entries lose `dev: true` because npm recomputed their dev
  reachability: @types/react-dom, escape-string-regexp, js-tokens,
  loose-envify, prop-types, react-is

Verified mechanically: 961 packages before and after, no additions, no
removals, and no change to any `version`, `resolved` or `integrity`
field. Isolated into its own commit so the real dependency change that
follows is reviewable instead of being buried in the reordering.

Co-authored-by: Cursor <cursoragent@cursor.com>

...

This commit is contained in:

Jesse_Chen

2026-08-17 14:57:18 +08:00

parent 9dc2948ab6

commit 809e0dbfb8

1 changed files with 3516 additions and 3522 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

frontend/package-lock.json

Generated

+3516 -3522

File diff suppressed because it is too large Load Diff