forked from CopilotKit/CopilotKit
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathpnpm-workspace.yaml
More file actions
51 lines (51 loc) · 2.55 KB
/
Copy pathpnpm-workspace.yaml
File metadata and controls
51 lines (51 loc) · 2.55 KB
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
packages:
- "packages/*"
- "examples/v1/*"
- "examples/v2/*"
- "examples/v2/*/apps/*"
- "examples/v2/react/*"
- "examples/v2/vue/*"
- "examples/v2/angular/*"
- "examples/v2/react-native/*"
- "examples/v2/runtime/*"
- "examples/showcases/generative-ui-playground"
# NOTE: `examples/showcases/reskinnable-demo` is intentionally NOT part of
# this pnpm workspace, for the same reason as `showcase/shell-dashboard`
# below: it ships its own lockfile and installs its `@copilotkit/*` and
# `@ag-ui/*` dependencies from npm rather than from `workspace:*`.
#
# It has to. Its agent is a Python deep agent whose subagents are only
# representable over AG-UI on the canary line
# (`@ag-ui/* 0.0.59-canary.1786716392.0` + `@copilotkit/* 1.62.2-canary…`) —
# the released `@ag-ui/client` 0.0.57 rejects `SUBAGENT_*` events in the HTTP
# transport before any middleware runs and kills the whole stream. Pinning
# those canaries as ROOT overrides would impose an unreleased protocol on
# every package in the monorepo for one app's benefit; keeping the demo out of
# the workspace confines them to the app that needs them.
#
# ⚠ KNOWN GAP, tracked as a follow-up: Nx discovers projects THROUGH the pnpm
# workspace (there is no `workspaceLayout` in `nx.json`), so removing the demo
# here also removes it from the repo-wide `nx run-many -t build`
# (`static_compat.yml`) and `-t check-types` (`static_quality.yml`) sweeps —
# verified: `nx show project deep-agents` and the other standalone showcases
# return "Could not find project". No workflow names this demo, so it is
# currently unbuilt and untype-checked in CI. It needs its own workflow job
# (`pnpm install && pnpm build && pnpm typecheck` in its directory), which is
# NOT in this change. Run the four gates locally until that lands.
- "examples/slack"
- "examples/teams"
- "!examples/v1/_legacy"
- "showcase/scripts"
# No npm lockfile here: installs with pnpm from the root pnpm-lock.yaml.
- "showcase/harness"
- "showcase/eval-webhook"
- "showcase/angular"
# NOTE: `showcase/shell-dashboard` is intentionally NOT part of this
# pnpm workspace. It's a flat, standalone Next.js app that ships its
# own package-lock.json and is built with `npm ci` (see its Dockerfile).
# Including it here would force it into the pnpm lockfile, which
# breaks its independent deploy path and invalidates the npm-based
# Docker build. `showcase/scripts` IS in the workspace because the
# harness package imports from it and both use pnpm.
onlyBuiltDependencies:
- better-sqlite3