Track package-lock.json for both the API and the UI
The caret ranges in ui/package.json (^4.5.1 viewer/client/datagrid, ^4.4.1 viewer-d3fc) let npm install resolve a newer Perspective on a fresh machine. That pairing is deliberate and load-bearing — 4.4.1 lacks the /inline export paths Pivot.jsx imports, and viewer-d3fc has no 4.5.x — so the resolved tree needs pinning, not just the ranges. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
1260873316
commit
e73326b615
4
.gitignore
vendored
4
.gitignore
vendored
@ -2,10 +2,10 @@
|
||||
.env
|
||||
|
||||
# Dependencies
|
||||
# Lockfiles ARE tracked — they pin the Perspective 4.5.1/4.4.1 pairing that the
|
||||
# caret ranges in ui/package.json would otherwise let drift. See docs/perspective.md.
|
||||
node_modules/
|
||||
ui/node_modules/
|
||||
package-lock.json
|
||||
ui/package-lock.json
|
||||
|
||||
# UI build output (generated — run `cd ui && npm run build`)
|
||||
public/
|
||||
|
||||
1678
package-lock.json
generated
Normal file
1678
package-lock.json
generated
Normal file
File diff suppressed because it is too large
Load Diff
4583
ui/package-lock.json
generated
Normal file
4583
ui/package-lock.json
generated
Normal file
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue
Block a user