@heretek-ai/opencode-teamwork-v2 0.0.0-stage → 0.5.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +22 -0
- package/README.md +387 -2
- package/agents/team/crafter.md +146 -0
- package/agents/team/falsifier.md +98 -0
- package/agents/team/orchestrator.md +136 -0
- package/agents/team/proof-worker.md +66 -0
- package/agents/team/proposer.md +76 -0
- package/agents/team/scout.md +93 -0
- package/agents/team/security-auditor.md +64 -0
- package/agents/team/sentinel.md +175 -0
- package/agents/team/synthesizer.md +108 -0
- package/agents/team/verifier.md +106 -0
- package/agents/team/worker.md +74 -0
- package/bin/opencode-teamwork.mjs +517 -0
- package/docs/ARTIFACTS.md +806 -0
- package/docs/GUARDRAILS.md +48 -0
- package/lib/doctor.mjs +280 -0
- package/lib/export.mjs +1119 -0
- package/lib/picker.mjs +132 -0
- package/lib/runs.mjs +165 -0
- package/lib/team.mjs +394 -0
- package/lib/timeline.mjs +713 -0
- package/package.json +68 -4
- package/plugins/opencode-teamwork/index.ts +232 -0
- package/plugins/opencode-teamwork/package.json +11 -0
- package/plugins/opencode-teamwork/tools.ts +2912 -0
- package/postinstall.mjs +71 -0
- package/scripts/lint-prompts.mjs +168 -0
- package/scripts/test-cost.mjs +242 -0
- package/scripts/test-doctor.mjs +287 -0
- package/scripts/test-engine.mjs +2041 -0
- package/scripts/test-export.mjs +540 -0
- package/scripts/test-timeline.mjs +1041 -0
package/package.json
CHANGED
|
@@ -1,6 +1,70 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@heretek-ai/opencode-teamwork-v2",
|
|
3
|
-
"version": "0.
|
|
4
|
-
"
|
|
5
|
-
"
|
|
6
|
-
|
|
3
|
+
"version": "0.5.10",
|
|
4
|
+
"description": "Antigravity-style multi-agent orchestration for OpenCode V2 — 11 agents, 7 commands, interactive model assignment on install.",
|
|
5
|
+
"keywords": [
|
|
6
|
+
"opencode",
|
|
7
|
+
"opencode-plugin",
|
|
8
|
+
"opencode-v2",
|
|
9
|
+
"agents",
|
|
10
|
+
"multi-agent",
|
|
11
|
+
"orchestration",
|
|
12
|
+
"teamwork",
|
|
13
|
+
"deepseek"
|
|
14
|
+
],
|
|
15
|
+
"license": "MIT",
|
|
16
|
+
"repository": {
|
|
17
|
+
"type": "git",
|
|
18
|
+
"url": "git+https://github.com/Heretek-AI/opencode-teamwork-v2.git"
|
|
19
|
+
},
|
|
20
|
+
"homepage": "https://github.com/Heretek-AI/opencode-teamwork-v2#readme",
|
|
21
|
+
"bugs": {
|
|
22
|
+
"url": "https://github.com/Heretek-AI/opencode-teamwork-v2/issues"
|
|
23
|
+
},
|
|
24
|
+
"type": "module",
|
|
25
|
+
"exports": {
|
|
26
|
+
".": "./plugins/opencode-teamwork/index.ts"
|
|
27
|
+
},
|
|
28
|
+
"main": "./plugins/opencode-teamwork/index.ts",
|
|
29
|
+
"bin": {
|
|
30
|
+
"opencode-teamwork": "bin/opencode-teamwork.mjs",
|
|
31
|
+
"opencode-teamwork-v2": "bin/opencode-teamwork.mjs"
|
|
32
|
+
},
|
|
33
|
+
"files": [
|
|
34
|
+
"agents",
|
|
35
|
+
"plugins",
|
|
36
|
+
"lib",
|
|
37
|
+
"bin",
|
|
38
|
+
"docs",
|
|
39
|
+
"!docs/re/**",
|
|
40
|
+
"scripts",
|
|
41
|
+
"postinstall.mjs",
|
|
42
|
+
"README.md",
|
|
43
|
+
"LICENSE"
|
|
44
|
+
],
|
|
45
|
+
"scripts": {
|
|
46
|
+
"postinstall": "node ./postinstall.mjs",
|
|
47
|
+
"lint:prompts": "node ./scripts/lint-prompts.mjs",
|
|
48
|
+
"test:cost": "node ./scripts/test-cost.mjs",
|
|
49
|
+
"test:engine": "node ./scripts/test-engine.mjs",
|
|
50
|
+
"test:doctor": "node ./scripts/test-doctor.mjs",
|
|
51
|
+
"test:timeline": "node ./scripts/test-timeline.mjs",
|
|
52
|
+
"test:export": "node ./scripts/test-export.mjs",
|
|
53
|
+
"test": "npm run lint:prompts && npm run test:cost && npm run test:engine && npm run test:doctor && npm run test:timeline && npm run test:export",
|
|
54
|
+
"init": "node ./bin/opencode-teamwork.mjs init",
|
|
55
|
+
"models": "node ./bin/opencode-teamwork.mjs models",
|
|
56
|
+
"status": "node ./bin/opencode-teamwork.mjs status",
|
|
57
|
+
"doctor": "node ./bin/opencode-teamwork.mjs doctor",
|
|
58
|
+
"timeline": "node ./bin/opencode-teamwork.mjs timeline",
|
|
59
|
+
"runs": "node ./bin/opencode-teamwork.mjs runs",
|
|
60
|
+
"inspect": "node ./bin/opencode-teamwork.mjs inspect",
|
|
61
|
+
"prune": "node ./bin/opencode-teamwork.mjs prune",
|
|
62
|
+
"export": "node ./bin/opencode-teamwork.mjs export"
|
|
63
|
+
},
|
|
64
|
+
"engines": {
|
|
65
|
+
"node": ">=18"
|
|
66
|
+
},
|
|
67
|
+
"publishConfig": {
|
|
68
|
+
"access": "public"
|
|
69
|
+
}
|
|
70
|
+
}
|
|
@@ -0,0 +1,232 @@
|
|
|
1
|
+
// @heretek-ai/opencode-teamwork-v2 — V2 port
|
|
2
|
+
//
|
|
3
|
+
// Original package: opencode-teamwork@0.2.1 (V1 plugin API)
|
|
4
|
+
// Ported to the OpenCode V2 plugin API (see https://opencode.ai/v2/docs/build/plugins).
|
|
5
|
+
//
|
|
6
|
+
// What changed vs the V1 plugin:
|
|
7
|
+
// * Default export is now an object definition `{ id, setup }` instead of the
|
|
8
|
+
// V1 async plugin function returning a `config` hook.
|
|
9
|
+
// * Agent registration moved OUT of the plugin. The V2 AgentEditor has no
|
|
10
|
+
// `add`, so plugins cannot create agents. The 10 `team/*` agents are
|
|
11
|
+
// installed as markdown files under ~/.config/opencode/agents/team/.
|
|
12
|
+
// * Commands are still registered by the plugin, via ctx.command.transform,
|
|
13
|
+
// which is the V2 replacement for the V1 `config` hook's command injection.
|
|
14
|
+
// * Command templates no longer use `{{ ... }}` handlebars (unsupported in V2)
|
|
15
|
+
// and rely on `$ARGUMENTS` substitution.
|
|
16
|
+
//
|
|
17
|
+
// Deliberately dependency-free at runtime: no import of @opencode/plugin so the
|
|
18
|
+
// loader never has to resolve node_modules for this file. The object shape below
|
|
19
|
+
// is exactly what Plugin.define({ id, setup }) produces.
|
|
20
|
+
|
|
21
|
+
import { registerTeamworkTools, registerTeamworkHooks } from "./tools.ts"
|
|
22
|
+
|
|
23
|
+
type CommandSpec = {
|
|
24
|
+
name: string
|
|
25
|
+
description: string
|
|
26
|
+
agent: string
|
|
27
|
+
template: string
|
|
28
|
+
}
|
|
29
|
+
|
|
30
|
+
const COMMANDS: CommandSpec[] = [
|
|
31
|
+
{
|
|
32
|
+
name: "teamwork",
|
|
33
|
+
description:
|
|
34
|
+
"Sentinel — main dispatcher. Loads a spec (or asks 1-2 questions), provisions a worktree, builds the DAG, dispatches workers + verifiers, iterates, merges. This is the user-facing /teamwork command.",
|
|
35
|
+
agent: "team/sentinel",
|
|
36
|
+
template: `$ARGUMENTS
|
|
37
|
+
|
|
38
|
+
Look in \`.opencode/teamwork/\` for a recent \`prompt_draft.md\`. If you find one, ask the user to confirm the session ID. If not, ask 1-2 short questions to pick the topology, then either run the crafter (via /teamwork-craft) or inline the answers and proceed.
|
|
39
|
+
|
|
40
|
+
Then:
|
|
41
|
+
|
|
42
|
+
0. Budget preflight: call \`teamwork_budget\`. If it reports console-credit budgeting applies (opencode/ models + opencode_console connected), call \`opencode_console_get_usage\`, compute \`remaining = min(limitDollars - spentDollars)\`, and ASK THE USER whether to use the FULL remaining budget or PARTIAL (half). Pass the choice to \`teamwork_plan\` as \`budgetUsd\` with \`budgetSource: "credits"\`.
|
|
43
|
+
1. Load the spec, then call the \`teamwork_plan\` tool to create the run — it returns the canonical \`SESSION_ID\`. Never use a session id read from a file. Provision the sentinel worktree OUTSIDE the repo, quoting both args: \`git worktree add "\${TEAMWORK_WORKTREES_DIR:-../.teamwork-worktrees}/$SESSION_ID/sentinel" -b "teamwork/base-$SESSION_ID"\` (skip if not in a git repo).
|
|
44
|
+
2. Build the DAG in \`.opencode/teamwork/<session-id>/plan.dag.json\`. Independent tasks run in parallel; dependent ones in topological order.
|
|
45
|
+
3. Dispatch workers in topological order. Each gets:
|
|
46
|
+
- Its own worktree
|
|
47
|
+
- A scoped \`spec.json\`
|
|
48
|
+
- Returns: \`patch.diff\` + \`summary.md\` + cost metrics
|
|
49
|
+
- On return: \`teamwork_cost({ taskId })\`, then \`teamwork_task_update\` with \`agent: "team/worker"\`
|
|
50
|
+
4. Dispatch verifiers against each worker's diff. Aggregated results go in \`.opencode/teamwork/<session-id>/verify/summary.json\`. On each verifier report: \`teamwork_cost({ taskId })\`, then \`teamwork_task_update\` with \`agent: "team/verifier"\`.
|
|
51
|
+
5. If FAIL, send the verifier's \`feedback_for_worker.md\` back to the worker for the next round. Loop until PASS, maxRounds, or budget exhausted.
|
|
52
|
+
6. When all tasks PASS, run the mandatory pre-merge security audit via @team/security-auditor and teamwork_security_audit. Once approved (PASS), merge the sentinel worktree back to the user's branch. On partial, present the partial + the open verification reports.
|
|
53
|
+
7. After the run completes (full or partial), perform the independent final verification: spawn a \`team/verifier\` agent to check the final merged result against the spec's acceptance criteria, then have it call \`teamwork_final_verify\`. That tool computes the verdict from the per-task reports and the security audit, stamps provenance, and writes \`.opencode/teamwork/$SESSION_ID/verify/final.json\` — it is the writer, so never hand-write that file. (\`teamwork_next\` only completes a run on a stamped report; a hand-written legacy report needs the explicit \`allowUnstamped: true\` bypass, which is recorded.)
|
|
54
|
+
|
|
55
|
+
Hard caps (override in the spec if the user asks):
|
|
56
|
+
- 4 rounds per task (6 for proof, 1 for small-focused, 24h for massive-proof)
|
|
57
|
+
- Budget: derived from opencode_console credits when available (full or partial, per the user), else the default $20 session budget
|
|
58
|
+
|
|
59
|
+
When done, write \`.opencode/teamwork/<session-id>/final.md\` and present. Tell the user:
|
|
60
|
+
- Which topology you chose
|
|
61
|
+
- How many rounds each task took
|
|
62
|
+
- Total cost (estimated)
|
|
63
|
+
- Path to the final artifact
|
|
64
|
+
- Any unresolved verification reports`,
|
|
65
|
+
},
|
|
66
|
+
{
|
|
67
|
+
name: "teamwork-craft",
|
|
68
|
+
description:
|
|
69
|
+
"Phase-1 prompt crafter. Runs the 9-step elicitation flow before a Teamwork run, produces prompt_draft.md. Use for any hard problem where you want a falsifiable spec before dispatching agents.",
|
|
70
|
+
agent: "team/crafter",
|
|
71
|
+
template: `$ARGUMENTS
|
|
72
|
+
|
|
73
|
+
The user wants to run a Teamwork session. Before dispatching agents, you need a spec.
|
|
74
|
+
|
|
75
|
+
Run the 9-step elicitation flow:
|
|
76
|
+
|
|
77
|
+
1. Elicit project idea (1-2 declarative sentences)
|
|
78
|
+
2. Identify ambiguity + scale (small-focused / iterative-coding / distributed-coding / proof / massive-proof / document-review)
|
|
79
|
+
3. Determine integrity mode (development / demo / benchmark)
|
|
80
|
+
4. Draft requirements $R_1 \\dots R_N$ (2-5 behavior-focused)
|
|
81
|
+
5. Design verification (forcing function — what makes the verifier say PASS)
|
|
82
|
+
6. Set acceptance criteria (markdown checkboxes for each $R_i$)
|
|
83
|
+
7. Configure model allocation (preset: anthropic/team/google/openai/free — or \`custom\` for per-role)
|
|
84
|
+
8. Set working directory
|
|
85
|
+
9. Assemble + validate (run the anti-pattern checks)
|
|
86
|
+
|
|
87
|
+
Save the spec to \`.opencode/teamwork/<session-id>/prompt_draft.md\`.
|
|
88
|
+
|
|
89
|
+
When the spec is approved by the user, they can run \`/teamwork <session-id>\` to dispatch the Sentinel.
|
|
90
|
+
|
|
91
|
+
If the user just wants speed, tell them: "Run \`/teamwork\` with your prompt. The Sentinel will ask the same 9 questions in compressed form. The wizard is the right tool for multi-hour / multi-day problems."`,
|
|
92
|
+
},
|
|
93
|
+
{
|
|
94
|
+
name: "team-orchestrate",
|
|
95
|
+
description:
|
|
96
|
+
"Legacy v1 orchestrator loop. Use /teamwork (sentinel) for new runs. This is the original propose/falsify/synthesize/verify loop without DAG, worktrees, or cost tracking.",
|
|
97
|
+
agent: "team/orchestrator",
|
|
98
|
+
template: `$ARGUMENTS
|
|
99
|
+
|
|
100
|
+
You are the legacy v1 orchestrator. The user has explicitly requested the v1 loop (or is running a project that hasn't migrated to v2).
|
|
101
|
+
|
|
102
|
+
Follow the v1 run loop:
|
|
103
|
+
|
|
104
|
+
1. Scout first.
|
|
105
|
+
2. Propose 3-5 candidates in parallel.
|
|
106
|
+
3. Falsify each one. Mandatory.
|
|
107
|
+
4. Synthesize (unless iterative-coding).
|
|
108
|
+
5. Verify.
|
|
109
|
+
6. If FAIL, log a pitfall and re-propose.
|
|
110
|
+
7. Present the final artifact at \`.opencode/teamwork/<session-id>/final.md\`.
|
|
111
|
+
|
|
112
|
+
If you want the v2 features (DAG engine, git worktrees per agent, typed artifact bus, cost tracking, prompt-crafter wizard), use \`/teamwork\` instead.`,
|
|
113
|
+
},
|
|
114
|
+
{
|
|
115
|
+
name: "team-propose",
|
|
116
|
+
description:
|
|
117
|
+
"Run only the propose step. Generates N candidate solutions in parallel and writes them under .opencode/teamwork/. Use when you want to inspect raw candidates before the falsifier step.",
|
|
118
|
+
agent: "team/orchestrator",
|
|
119
|
+
template: `$ARGUMENTS
|
|
120
|
+
|
|
121
|
+
The user wants raw candidates, not a full Teamwork run. Do this:
|
|
122
|
+
|
|
123
|
+
1. Pick a pattern from the prompt (default: distributed-coding).
|
|
124
|
+
2. Run scout first to gather context.
|
|
125
|
+
3. Dispatch \`@team/proposer\` N=3 times in parallel, each with a different strategy framing. If no strategy framing is obvious, use these defaults:
|
|
126
|
+
- Candidate 1: "the textbook approach"
|
|
127
|
+
- Candidate 2: "an unconventional / contrarian angle"
|
|
128
|
+
- Candidate 3: "the minimal change that could work"
|
|
129
|
+
4. Write the candidates to \`.opencode/teamwork/<session-id>/candidates/cand-1.md\` through \`cand-3.md\`.
|
|
130
|
+
5. STOP after writing the candidates. Do not run falsifier, synthesizer, or verifier. The user will inspect and decide next.
|
|
131
|
+
|
|
132
|
+
Report back: where the candidates are, a 1-line summary of each, and any patterns you noticed across them (e.g. "all 3 candidates picked the same library — this might be the wrong choice").`,
|
|
133
|
+
},
|
|
134
|
+
{
|
|
135
|
+
name: "team-falsify",
|
|
136
|
+
description:
|
|
137
|
+
"Run only the falsifier step on existing candidates. Use after /team-propose to get adversarial critique before deciding to synthesize.",
|
|
138
|
+
agent: "team/orchestrator",
|
|
139
|
+
template: `$ARGUMENTS
|
|
140
|
+
|
|
141
|
+
The user wants falsifier critiques of existing candidates. Do this:
|
|
142
|
+
|
|
143
|
+
1. List the candidates in \`.opencode/teamwork/<session-id>/candidates/\`.
|
|
144
|
+
2. For each candidate, dispatch \`@team/falsifier\`. Falsifiers run in parallel.
|
|
145
|
+
3. Write the critiques to \`.opencode/teamwork/<session-id>/critiques/crit-<n>.md\`.
|
|
146
|
+
4. After all critiques are in, write a meta-summary at \`.opencode/teamwork/<session-id>/critiques/summary.md\`:
|
|
147
|
+
- How many candidates were killed (FATAL).
|
|
148
|
+
- How many have SERIOUS findings.
|
|
149
|
+
- How many pass with MINOR findings only.
|
|
150
|
+
- Which failure modes appear across multiple candidates (these are likely real and the proposers should be told).
|
|
151
|
+
5. STOP. Do not synthesize. The user will decide.
|
|
152
|
+
|
|
153
|
+
Report back: the summary and a recommendation ("synthesis likely unnecessary, all 3 are broken in the same way" or "candidates diverge enough that synthesis will be hard" or "one clear winner, ready to verify").`,
|
|
154
|
+
},
|
|
155
|
+
{
|
|
156
|
+
name: "team-synthesize",
|
|
157
|
+
description:
|
|
158
|
+
"Run the synthesizer on existing candidates + critiques. Use after /team-falsify when candidates have been critiqued and a merge is needed.",
|
|
159
|
+
agent: "team/orchestrator",
|
|
160
|
+
template: `$ARGUMENTS
|
|
161
|
+
|
|
162
|
+
The user wants a synthesis of existing candidates and their critiques. Do this:
|
|
163
|
+
|
|
164
|
+
1. Read all candidates in \`.opencode/teamwork/<session-id>/candidates/\`.
|
|
165
|
+
2. Read all critiques in \`.opencode/teamwork/<session-id>/critiques/\`.
|
|
166
|
+
3. Read the pitfall registry \`.opencode/teamwork/<session-id>/pitfalls.md\` if it exists.
|
|
167
|
+
4. Dispatch \`@team/synthesizer\` with all of the above.
|
|
168
|
+
5. Write the synthesis to \`.opencode/teamwork/<session-id>/synthesis/syn-1.md\`.
|
|
169
|
+
6. STOP. Do not verify. The user will run /teamwork or call the verifier directly.
|
|
170
|
+
|
|
171
|
+
Report back: where the synthesis is, what was kept from each source candidate, and any new failure modes the synthesizer flagged. If the synthesis was inconclusive, say so explicitly and explain why.`,
|
|
172
|
+
},
|
|
173
|
+
{
|
|
174
|
+
name: "team-review",
|
|
175
|
+
description:
|
|
176
|
+
"Run the verifier on the current synthesis or candidate. Use after /team-synthesize (or directly on a candidate) to get a binary PASS/FAIL with evidence.",
|
|
177
|
+
agent: "team/orchestrator",
|
|
178
|
+
template: `$ARGUMENTS
|
|
179
|
+
|
|
180
|
+
The user wants verification of a specific artifact. Do this:
|
|
181
|
+
|
|
182
|
+
1. Find the artifact: the latest file in \`.opencode/teamwork/<session-id>/synthesis/\`, or fall back to the latest in \`candidates/\` if no synthesis exists.
|
|
183
|
+
2. Dispatch \`@team/verifier\` with the artifact and the relevant critiques.
|
|
184
|
+
3. Write the verification report to \`.opencode/teamwork/<session-id>/verify/v-<n>.md\`.
|
|
185
|
+
4. STOP. The user will read the report and decide.
|
|
186
|
+
|
|
187
|
+
Report back: PASS or FAIL, a 1-line summary of the checks, and (if FAIL) the specific commands to reproduce. Do not propose a fix.`,
|
|
188
|
+
},
|
|
189
|
+
]
|
|
190
|
+
|
|
191
|
+
// Best-effort self-heal: when this file is loaded from the published npm
|
|
192
|
+
// package (rather than a hand-vendored copy) make sure the `team/*` agent
|
|
193
|
+
// markdown files exist in the OpenCode config directory. Only files that are
|
|
194
|
+
// completely missing are created; existing agents are never rewritten, so a
|
|
195
|
+
// user's model choices from `opencode-teamwork init` are preserved. When the
|
|
196
|
+
// plugin is vendored without the new package layout the import fails and this
|
|
197
|
+
// quietly does nothing.
|
|
198
|
+
async function ensureAgentsInstalled() {
|
|
199
|
+
try {
|
|
200
|
+
const lib = await import("../../lib/team.mjs")
|
|
201
|
+
const { fileURLToPath } = await import("node:url")
|
|
202
|
+
lib.ensureAgents({ packageRoot: fileURLToPath(new URL("../../", import.meta.url)) })
|
|
203
|
+
} catch {
|
|
204
|
+
// Vendored copy without lib/, or filesystem not writable. Not fatal.
|
|
205
|
+
}
|
|
206
|
+
}
|
|
207
|
+
|
|
208
|
+
export default {
|
|
209
|
+
id: "opencode-teamwork",
|
|
210
|
+
async setup(ctx: any) {
|
|
211
|
+
await ensureAgentsInstalled()
|
|
212
|
+
const root = (ctx?.location?.directory as string) || process.cwd()
|
|
213
|
+
await registerTeamworkTools(ctx, root)
|
|
214
|
+
await registerTeamworkHooks(ctx, root)
|
|
215
|
+
await ctx.command.transform((editor: any) => {
|
|
216
|
+
for (const cmd of COMMANDS) {
|
|
217
|
+
editor.add({
|
|
218
|
+
name: cmd.name,
|
|
219
|
+
description: cmd.description,
|
|
220
|
+
execute: async ({ sessionID, prompt, delivery }: any) => {
|
|
221
|
+
// V1 commands selected an agent via frontmatter; V2 plugin commands
|
|
222
|
+
// must switch the session agent explicitly.
|
|
223
|
+
await ctx.session.switchAgent({ sessionID, agent: cmd.agent })
|
|
224
|
+
const args = typeof prompt?.text === "string" ? prompt.text : ""
|
|
225
|
+
const text = cmd.template.split("$ARGUMENTS").join(args)
|
|
226
|
+
await ctx.session.prompt({ ...prompt, sessionID, text, delivery })
|
|
227
|
+
},
|
|
228
|
+
})
|
|
229
|
+
}
|
|
230
|
+
})
|
|
231
|
+
},
|
|
232
|
+
}
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "opencode-teamwork",
|
|
3
|
+
"version": "0.5.0",
|
|
4
|
+
"private": true,
|
|
5
|
+
"type": "module",
|
|
6
|
+
"description": "Vendored V2 port of opencode-teamwork (registers the /teamwork command family, ships the teamwork_* engine tools).",
|
|
7
|
+
"main": "./index.ts",
|
|
8
|
+
"exports": {
|
|
9
|
+
".": "./index.ts"
|
|
10
|
+
}
|
|
11
|
+
}
|