dormouse/pnpm-workspace.yaml at main · diffplug/dormouse · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
packages:
  - canopy
  - dor
  - dor-lib-common
  - hosted
  - lib
  - relay
  - remote-lib-common
  - standalone
  - standalone/sidecar
  - vscode-ext
  - website
allowBuilds:
  cpu-features: false
  protobufjs: false
  ssh2: false
  workerd: true
  "@swc/core": true
  "@vscode/vsce-sign": false
  esbuild: true
  keytar: false
  node-pty: true
  sharp: true
# An unmet peer fails the install instead of warning, so a bump that leaves a
# shared library outside a dependent's range (pgstencil's kysely/hono, the
# @hono adapters) goes red in its own PR. Widen deliberately below, with a reason.
strictPeerDependencies: true
peerDependencyRules:
  allowedVersions:
    "react-helmet-async>react": ^19.0.0
    "react-helmet-async>react-dom": ^19.0.0
    # `relay` runs @hono/node-server 2.x; no @hono/node-ws release supports it
    # (1.3.1 is latest and declares `^1.19.11`), so this is a deliberate widening
    # rather than a missing upgrade. It is safe because the peer is nominal:
    # @hono/node-ws imports `hono/ws`, `ws` and `node:http` only, never
    # @hono/node-server. What it actually needs is `env.incoming` to be a
    # `node:http` IncomingMessage — and it supplies that env itself when
    # `injectWebSocket` re-dispatches the upgrade request — plus a
    # `node:http`/`node:http2` server that emits `upgrade`. node-server 2.x still
    # types `HttpBindings.incoming` as `IncomingMessage`. Drop this the moment a
    # node-ws release widens the range; `relay/test/*.test.mjs` covers the relay
    # sockets that would break first.
    "@hono/node-ws>@hono/node-server": ^2.0.0
minimumReleaseAge: 1440
overrides:
  pgstencil: file:vendor/pgstencil-0.1.0.tgz
  '@pgstencil/auth': file:vendor/pgstencil-auth-0.1.0.tgz