omnigent/pnpm-workspace.yaml at main · omnigent-ai/omnigent · 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
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
packages:
  - 'web'
  - 'web/electron'
  - '.github/ci-deps'
  - 'editors/vscode'
  - 'deploy/cloudflare'

settings:
  # 7-day dependency cooldown, mirroring the Python-side exclude-newer = "P7D" in uv.toml.
  minimumReleaseAge: 10080
  autoInstallPeers: false
  strictPeerDependencies: false

# jest-dom doesn't declare vitest as a (peer) dependency, so under pnpm's store
# layout its `declare module "vitest"` matcher-type augmentation can't resolve
# vitest and silently fails to merge — `tsc` then loses every DOM matcher
# (toBeInTheDocument, toHaveClass, …) though they work at runtime. Re-enable the
# peer so the augmentation resolves. Drop once jest-dom ships the peer upstream.
packageExtensions:
  '@testing-library/jest-dom':
    peerDependencies:
      vitest: '*'

catalog:
  react: ^18.2.0
  react-dom: ^18.2.0
  shiki: 4.2.0

overrides:
  # Build-tool pins that match the legacy npm lockfile. Removing them allowed pnpm
  # to resolve newer Vite/Tailwind patches whose new bundler/chunking produced a
  # broken split of the Shiki bundle and lost the PDF worker asset.
  vite: 8.1.0
  tailwindcss: 4.3.1
  '@tailwindcss/vite': 4.3.1
  '@tailwindcss/node': 4.3.1
  '@tailwindcss/postcss': 4.3.1
  jiti: 2.7.0
  lightningcss: 1.32.0
  postcss: 8.5.18
  linkify-it: 5.0.2
  shiki: "catalog:"
  react: "catalog:"
  react-dom: "catalog:"
  dompurify: ^3.4.0
  '@shikijs/core': 4.2.0
  '@shikijs/engine-javascript': 4.2.0
  '@shikijs/engine-oniguruma': 4.2.0
  '@shikijs/langs': 4.2.0
  '@shikijs/themes': 4.2.0
  '@shikijs/types': 4.2.0
  '@shikijs/transformers': 4.2.0
  '@tiptap/core': 3.23.4
  '@tiptap/extension-blockquote': 3.23.4
  '@tiptap/extension-bold': 3.23.4
  '@tiptap/extension-bubble-menu': 3.23.4
  '@tiptap/extension-bullet-list': 3.23.4
  '@tiptap/extension-code': 3.23.4
  '@tiptap/extension-code-block': 3.23.4
  '@tiptap/extension-document': 3.23.4
  '@tiptap/extension-dropcursor': 3.23.4
  '@tiptap/extension-floating-menu': 3.23.4
  '@tiptap/extension-gapcursor': 3.23.4
  '@tiptap/extension-hard-break': 3.23.4
  '@tiptap/extension-heading': 3.23.4
  '@tiptap/extension-horizontal-rule': 3.23.4
  '@tiptap/extension-image': 3.23.4
  '@tiptap/extension-italic': 3.23.4
  '@tiptap/extension-link': 3.23.4
  '@tiptap/extension-list': 3.23.4
  '@tiptap/extension-list-item': 3.23.4
  '@tiptap/extension-list-keymap': 3.23.4
  '@tiptap/extension-ordered-list': 3.23.4
  '@tiptap/extension-paragraph': 3.23.4
  '@tiptap/extension-strike': 3.23.4
  '@tiptap/extension-table': 3.23.4
  '@tiptap/extension-text': 3.23.4
  '@tiptap/extension-underline': 3.23.4
  '@tiptap/extensions': 3.23.4
  '@tiptap/markdown': 3.23.4
  '@tiptap/pm': 3.23.4
  '@tiptap/react': 3.23.4
  '@tiptap/starter-kit': 3.23.4
  express-rate-limit>ip-address: ^10.1.1

allowBuilds:
  '@anthropic-ai/claude-code': true
  '@google/genai': true
  '@vscode/vsce-sign': true
  canvas: true
  # electron + playwright: the desktop recording lane (web/electron/e2e/) needs
  # their postinstall scripts to run — electron downloads its ~100MB runtime
  # binary and playwright its driver. Without these, `pnpm install` in the
  # electron package "succeeds" but leaves the binaries absent, so the lane
  # can't launch. Dev/test only (both are web/electron devDependencies; not
  # bundled into the shipped app).
  electron: true
  electron-winstaller: true
  esbuild: true
  keytar: true
  msw: true
  playwright: true
  protobufjs: true
  sharp: true
  workerd: true