Luigit
repositories / pi-ext

pi-ext

bugabingas pi extensions

owned by admin

DEPENDENCIES.md

Raw
Rendered preview

Dependency compatibility

Prefer "*" for latest stable releases, with reproducibility supplied by package-lock.json and mise.lock. Run mise run //:bump for deliberate updates; //:lock alone reconciles manifests without upgrading every existing resolution. Compare actual lockfile resolutions with registry latest tags before verifying compatibility. Npm may retain older satisfying versions to deduplicate dependencies even after an update.

Current constraints

  • Replace only typed-rest-client@2.3.1 with 2.3.0 through a version-scoped override because 2.3.1 pins vulnerable qs@6.15.1. Version 2.3.0 remains within Stryker's ~2.3.0 requirement and allows patched qs@6.17.1; npm package diff shows no shipped implementation changes between those client versions. This override does not constrain future client releases and should be removed when the affected dependency chain moves past 2.3.1.
  • Canvas uses major 18 for react, react-dom, @types/react, and @types/react-dom because Excalidraw 0.18.1 pins @radix-ui/react-tabs@1.0.2, whose React peers exclude major 19. Remove these constraints when Excalidraw's dependency graph supports newer React.
  • TypeBox development uses "*", currently resolved at 1.4.4 separately from Pi 1.5.0's exact 1.3.27 dependency. Pi's extension loader aliases TypeBox to its own copy at runtime, so development resolution alone does not establish runtime compatibility.
  • @lydell/node-pty uses "*", but its upstream latest tag currently points to 1.2.0-beta.18. This is an upstream prerelease on the normal release channel, not an opted-in beta tag.
# Dependency compatibility

Prefer `"*"` for latest stable releases, with reproducibility supplied by `package-lock.json` and `mise.lock`.
Run `mise run //:bump` for deliberate updates; `//:lock` alone reconciles manifests without upgrading every existing resolution.
Compare actual lockfile resolutions with registry `latest` tags before verifying compatibility.
Npm may retain older satisfying versions to deduplicate dependencies even after an update.

## Current constraints

- Replace only `typed-rest-client@2.3.1` with `2.3.0` through a version-scoped override because `2.3.1` pins vulnerable `qs@6.15.1`.
  Version `2.3.0` remains within Stryker's `~2.3.0` requirement and allows patched `qs@6.17.1`; npm package diff shows no shipped implementation changes between those client versions.
  This override does not constrain future client releases and should be removed when the affected dependency chain moves past `2.3.1`.
- Canvas uses major `18` for `react`, `react-dom`, `@types/react`, and `@types/react-dom` because Excalidraw `0.18.1` pins `@radix-ui/react-tabs@1.0.2`, whose React peers exclude major `19`.
  Remove these constraints when Excalidraw's dependency graph supports newer React.
- TypeBox development uses `"*"`, currently resolved at `1.4.4` separately from Pi `1.5.0`'s exact `1.3.27` dependency.
  Pi's extension loader aliases TypeBox to its own copy at runtime, so development resolution alone does not establish runtime compatibility.
- `@lydell/node-pty` uses `"*"`, but its upstream `latest` tag currently points to `1.2.0-beta.18`.
  This is an upstream prerelease on the normal release channel, not an opted-in beta tag.