pi-jarvis 1.1.5 → 1.3.0
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/AGENTS.md +29 -0
- package/README.md +273 -61
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +483 -23
- package/dist/index.js.map +1 -1
- package/dist/jarvis-config.d.ts +25 -0
- package/dist/jarvis-config.d.ts.map +1 -0
- package/dist/jarvis-config.js +132 -0
- package/dist/jarvis-config.js.map +1 -0
- package/dist/main-context.js +7 -7
- package/dist/main-context.js.map +1 -1
- package/dist/main-session-state.d.ts +2 -1
- package/dist/main-session-state.d.ts.map +1 -1
- package/dist/main-session-state.js +18 -10
- package/dist/main-session-state.js.map +1 -1
- package/dist/overlay.d.ts +3 -0
- package/dist/overlay.d.ts.map +1 -1
- package/dist/overlay.js +85 -49
- package/dist/overlay.js.map +1 -1
- package/dist/session-ref.d.ts.map +1 -1
- package/dist/session-ref.js +1 -4
- package/dist/session-ref.js.map +1 -1
- package/dist/side-session.d.ts +9 -0
- package/dist/side-session.d.ts.map +1 -1
- package/dist/side-session.js +137 -9
- package/dist/side-session.js.map +1 -1
- package/package.json +6 -5
- package/dist/mcp-policy.d.ts +0 -2
- package/dist/mcp-policy.d.ts.map +0 -1
- package/dist/mcp-policy.js +0 -2
- package/dist/mcp-policy.js.map +0 -1
package/AGENTS.md
ADDED
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
# pi-jarvis Agent Notes
|
|
2
|
+
|
|
3
|
+
## Project Scope
|
|
4
|
+
- `pi-jarvis` is a Pi extension that opens a `/jarvis` side-conversation overlay.
|
|
5
|
+
- Core runtime files: `index.ts`, `side-session.ts`, `overlay.ts`, `jarvis-config.ts`, `session-ref.ts`.
|
|
6
|
+
|
|
7
|
+
## Current `/jarvis-model` and `/jarvis-thinking` Behavior
|
|
8
|
+
- `/jarvis-model` with no request opens a model picker when Pi has a UI.
|
|
9
|
+
- `/jarvis-model <provider/model>` writes a project-scoped override to `.pi/jarvis.json`.
|
|
10
|
+
- `/jarvis-model --global <provider/model>` writes the default global override to the active Pi agent directory's `extensions/pi-jarvis.json` (by default `~/.pi/agent/extensions/pi-jarvis.json`).
|
|
11
|
+
- `/jarvis-model [--project|--global] follow-main` stores a scoped `follow-main` override.
|
|
12
|
+
- `/jarvis-model [--project|--global] clear` removes that scope's override so fallback applies.
|
|
13
|
+
- `/jarvis-thinking [--project|--global] auto|follow-main|off|minimal|low|medium|high|xhigh` stores a scoped thinking override without changing the main session thinking level.
|
|
14
|
+
- `/jarvis-thinking [--project|--global] clear` removes that scope's thinking override so fallback applies.
|
|
15
|
+
- Resolution order is: project config, then global config, then built-in defaults (`follow-main` for model, `auto` for thinking).
|
|
16
|
+
- `auto` thinking follows main only when `/jarvis` follows the main model; pinned `/jarvis` models default to thinking `off`.
|
|
17
|
+
- `follow-main` thinking follows the main thinking level regardless of model selection, except xAI `/jarvis` models force thinking `off`.
|
|
18
|
+
- `/compact`, `/tree`, and `/new` entered inside `/jarvis` operate on the isolated `/jarvis` side-session, not the main Pi session.
|
|
19
|
+
- `Note main` and `Redirect` stay disabled when the active `/jarvis` model is incompatible with bridge tools.
|
|
20
|
+
|
|
21
|
+
## Validation
|
|
22
|
+
- Run `npm test` for full validation.
|
|
23
|
+
- Run `npm run build` before release packaging.
|
|
24
|
+
|
|
25
|
+
## Docs To Keep In Sync
|
|
26
|
+
- `README.md`
|
|
27
|
+
- `CHANGELOG.md`
|
|
28
|
+
- `package.json` version
|
|
29
|
+
- this `AGENTS.md` when command/config behavior changes
|
package/README.md
CHANGED
|
@@ -1,109 +1,322 @@
|
|
|
1
1
|
# pi-jarvis
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
<div align="center">
|
|
4
4
|
|
|
5
|
-
##
|
|
5
|
+
## A cinematic side-conversation overlay for Pi
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
**Open a second lane of thought without derailing the main session.**
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
`pi-jarvis` adds `/jarvis`: a polished overlay where you can ask for status, inspect the repo when you explicitly allow it, and send a quiet note or a confirmed redirect back to the main lane.
|
|
10
10
|
|
|
11
|
-
-
|
|
12
|
-
-
|
|
13
|
-
|
|
14
|
-
-
|
|
15
|
-
|
|
16
|
-
|
|
11
|
+
[](https://www.npmjs.com/package/pi-jarvis)
|
|
12
|
+
[](./LICENSE)
|
|
13
|
+
[](https://github.com/fluxgear/pi-jarvis)
|
|
14
|
+
[](./package.json)
|
|
15
|
+
|
|
16
|
+
<p>
|
|
17
|
+
<strong>Persistent side session</strong> ·
|
|
18
|
+
<strong>Live main-session awareness</strong> ·
|
|
19
|
+
<strong>Permission-gated tools</strong> ·
|
|
20
|
+
<strong>Safe redirect flow</strong>
|
|
21
|
+
</p>
|
|
22
|
+
|
|
23
|
+
</div>
|
|
24
|
+
|
|
25
|
+
---
|
|
26
|
+
|
|
27
|
+
## The pitch
|
|
28
|
+
|
|
29
|
+
The main Pi session should stay on the critical path.
|
|
30
|
+
|
|
31
|
+
`/jarvis` gives you a **second cockpit** for the work that should not interrupt that primary flow:
|
|
32
|
+
|
|
33
|
+
- checking what the main agent is doing right now
|
|
34
|
+
- seeing what changed since the last `/jarvis` turn
|
|
35
|
+
- asking for triage, summaries, or a second opinion
|
|
36
|
+
- inspecting the repo with local tools when you turn them on
|
|
37
|
+
- sending a non-interrupting note back to the main session
|
|
38
|
+
- redirecting the main session only after explicit confirmation
|
|
39
|
+
|
|
40
|
+
> Think of it as a side conversation with real context, not a detached scratchpad.
|
|
41
|
+
|
|
42
|
+
### Typical prompts
|
|
43
|
+
|
|
44
|
+
- *"What is the main agent doing right now?"*
|
|
45
|
+
- *"Summarize the last validation failure and tell me what matters."*
|
|
46
|
+
- *"Check this file while the main session keeps moving."*
|
|
47
|
+
- *"Compare what changed since my last `/jarvis` turn."*
|
|
48
|
+
- *"Redirect the main session, but make me confirm it first."*
|
|
49
|
+
|
|
50
|
+
---
|
|
51
|
+
|
|
52
|
+
## At a glance
|
|
53
|
+
|
|
54
|
+
| Capability | What you get |
|
|
55
|
+
|---|---|
|
|
56
|
+
| **Persistent side lane** | `/jarvis` keeps its own isolated conversation state and restores prior side-session history |
|
|
57
|
+
| **Live awareness** | Jarvis sees the current main-session summary plus a delta since the last `/jarvis` turn |
|
|
58
|
+
| **Permission-gated tools** | Local `read`, `bash`, `edit`, `write`, and optional `mcp` stay off until you enable them |
|
|
59
|
+
| **Safe main-session handoff** | `Note main` is quiet; `Redirect` is confirmation-gated |
|
|
60
|
+
| **Independent model control** | Follow the main model or pin `/jarvis` to a separate model |
|
|
61
|
+
| **Cleaner UX** | Thinking-step streaming is collapsed into a cleaner animated fallback |
|
|
62
|
+
|
|
63
|
+
---
|
|
64
|
+
|
|
65
|
+
## How it fits into Pi
|
|
66
|
+
|
|
67
|
+
```mermaid
|
|
68
|
+
flowchart LR
|
|
69
|
+
U[You] -->|primary work| M[Main Pi session]
|
|
70
|
+
U -->|open /jarvis| J[Jarvis overlay]
|
|
71
|
+
M -->|summary + recent delta| J
|
|
72
|
+
J -->|Repo tools enabled| R[Local tools\nread • bash • edit • write]
|
|
73
|
+
J -->|optional| X[MCP]
|
|
74
|
+
J -. Note main .-> M
|
|
75
|
+
J -. Redirect after confirmation .-> M
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
### Operating model
|
|
79
|
+
|
|
80
|
+
```mermaid
|
|
81
|
+
flowchart TD
|
|
82
|
+
A[Main session keeps moving] --> B[/jarvis opens in overlay]
|
|
83
|
+
B --> C[Jarvis sees current main-session context]
|
|
84
|
+
C --> D{What do you need?}
|
|
85
|
+
D -->|Status / summary / analysis| E[Jarvis handles the side task]
|
|
86
|
+
D -->|Repo inspection| F[Enable Repo tools]
|
|
87
|
+
D -->|Influence the main lane| G[Enable Note main or Redirect]
|
|
88
|
+
G --> H{Redirect?}
|
|
89
|
+
H -->|Yes| I[Per-send confirmation]
|
|
90
|
+
H -->|No| J[Quiet follow-up note]
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
---
|
|
94
|
+
|
|
95
|
+
## Why use `/jarvis` instead of the main lane?
|
|
96
|
+
|
|
97
|
+
Use `/jarvis` when you want:
|
|
98
|
+
|
|
99
|
+
- a second opinion without changing the primary plan yet
|
|
100
|
+
- a quick repo inspection while the main agent keeps moving
|
|
101
|
+
- a compact explanation of current progress or validation state
|
|
102
|
+
- a controlled way to send guidance back to the main session
|
|
103
|
+
|
|
104
|
+
Stay in the main lane when you want:
|
|
105
|
+
|
|
106
|
+
- the main plan to change immediately
|
|
107
|
+
- the main session itself to execute the next step directly
|
|
108
|
+
- no side conversation overhead at all
|
|
109
|
+
|
|
110
|
+
---
|
|
17
111
|
|
|
18
112
|
## Quick start
|
|
19
113
|
|
|
20
|
-
### 1
|
|
114
|
+
### 1) Install
|
|
21
115
|
|
|
22
116
|
```bash
|
|
23
117
|
npm install pi-jarvis
|
|
24
118
|
```
|
|
25
119
|
|
|
26
|
-
### 2
|
|
120
|
+
### 2) Register the extension in Pi
|
|
27
121
|
|
|
28
|
-
Use the published entrypoint:
|
|
122
|
+
Use the package's published extension entrypoint:
|
|
29
123
|
|
|
30
124
|
```text
|
|
31
125
|
./dist/index.js
|
|
32
126
|
```
|
|
33
127
|
|
|
34
|
-
This package is
|
|
128
|
+
This package is meant to run **inside a Pi installation** that provides the required peer dependencies.
|
|
35
129
|
|
|
36
|
-
### 3
|
|
130
|
+
### 3) Open Jarvis
|
|
37
131
|
|
|
38
132
|
```bash
|
|
39
133
|
/jarvis
|
|
40
134
|
```
|
|
41
135
|
|
|
42
|
-
|
|
136
|
+
Or open it and send the first message immediately:
|
|
43
137
|
|
|
44
138
|
```bash
|
|
45
|
-
/jarvis
|
|
139
|
+
/jarvis summarize the last validation failure and suggest the fastest next move
|
|
46
140
|
```
|
|
47
141
|
|
|
48
|
-
|
|
142
|
+
### 4) Turn on more power only when you want it
|
|
49
143
|
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
144
|
+
- leave `Repo tools` off for pure context / analysis
|
|
145
|
+
- turn `Repo tools` on when you want local `read`, `bash`, `edit`, `write`, and optional `mcp`
|
|
146
|
+
- turn `Note main` on when you want Jarvis to quietly message the main session
|
|
147
|
+
- turn `Redirect` on when you want Jarvis to propose a redirect that you still explicitly confirm
|
|
53
148
|
|
|
54
|
-
|
|
149
|
+
---
|
|
150
|
+
|
|
151
|
+
## Command surface
|
|
55
152
|
|
|
56
153
|
### `/jarvis`
|
|
57
|
-
Opens the side overlay. If
|
|
154
|
+
Opens the side overlay. If text follows the command, that text becomes the first side-session prompt.
|
|
155
|
+
|
|
156
|
+
### `/jarvis-model`
|
|
157
|
+
When Pi has a UI, running `/jarvis-model` with no argument opens a model picker instead of requiring an exact provider/model string.
|
|
158
|
+
|
|
159
|
+
### `/jarvis-model [--project|--global] <provider/model>`
|
|
160
|
+
Pins `/jarvis` to a specific model without changing the main session model. A plain `/jarvis-model <provider/model>` writes a **project-local** override to `.pi/jarvis.json`.
|
|
161
|
+
|
|
162
|
+
### `/jarvis-model [--project|--global] follow-main`
|
|
163
|
+
Restores the chosen scope to `follow-main`. A project-scoped `follow-main` override still wins over a global pinned setting.
|
|
164
|
+
|
|
165
|
+
### `/jarvis-model [--project|--global] clear`
|
|
166
|
+
Removes the selected scope so `/jarvis` falls back through the remaining config layers to the built-in default.
|
|
58
167
|
|
|
59
|
-
### `/jarvis-
|
|
60
|
-
|
|
168
|
+
### `/jarvis-thinking [--project|--global] auto|follow-main|off|minimal|low|medium|high|xhigh`
|
|
169
|
+
Sets the thinking level used by `/jarvis` without changing the main session thinking level. A plain `/jarvis-thinking <level>` writes a **project-local** override to `.pi/jarvis.json`.
|
|
61
170
|
|
|
62
|
-
|
|
63
|
-
|
|
171
|
+
- `auto` preserves the built-in behavior: follow the main thinking level only when `/jarvis` follows the main model; pinned `/jarvis` models use `off`.
|
|
172
|
+
- `follow-main` follows the main thinking level even when `/jarvis` is pinned to a separate model.
|
|
173
|
+
- Explicit levels pin `/jarvis` thinking to that level.
|
|
174
|
+
- xAI `/jarvis` models still force thinking `off`.
|
|
64
175
|
|
|
65
|
-
|
|
176
|
+
### `/jarvis-thinking [--project|--global] clear`
|
|
177
|
+
Removes the selected scope so `/jarvis` thinking falls back through the remaining config layers to the built-in `auto` default.
|
|
66
178
|
|
|
67
|
-
|
|
179
|
+
### Side-session commands inside `/jarvis`
|
|
180
|
+
The `/jarvis` input handles a small set of built-in commands against the isolated side-session:
|
|
68
181
|
|
|
69
|
-
- the
|
|
70
|
-
- the
|
|
71
|
-
-
|
|
72
|
-
-
|
|
182
|
+
- `/compact [instructions]` compacts the `/jarvis` conversation context.
|
|
183
|
+
- `/tree` prints the `/jarvis` session tree with entry IDs.
|
|
184
|
+
- `/tree <entry-id>` navigates the `/jarvis` session tree to that entry.
|
|
185
|
+
- `/tree --summarize <entry-id> [instructions]` navigates and summarizes the branch being left.
|
|
186
|
+
- `/new` starts a fresh `/jarvis` side-session without changing the main Pi session.
|
|
187
|
+
|
|
188
|
+
---
|
|
189
|
+
|
|
190
|
+
## Model and thinking resolution
|
|
191
|
+
|
|
192
|
+
```mermaid
|
|
193
|
+
flowchart TD
|
|
194
|
+
A[Project config\n.pi/jarvis.json] -->|if present| B{valid?}
|
|
195
|
+
B -->|yes| P[Use project selection]
|
|
196
|
+
B -->|no or missing| C[Global config\n<agentDir>/extensions/pi-jarvis.json]
|
|
197
|
+
C -->|if present| D{valid?}
|
|
198
|
+
D -->|yes| G[Use global selection]
|
|
199
|
+
D -->|no or missing| E[Built-in default]
|
|
200
|
+
E --> F[follow-main]
|
|
201
|
+
```
|
|
73
202
|
|
|
74
|
-
|
|
203
|
+
### Resolution order
|
|
75
204
|
|
|
76
|
-
|
|
77
|
-
- `Note main`
|
|
78
|
-
- `Redirect`
|
|
205
|
+
Both model and thinking settings resolve through the same config layers:
|
|
79
206
|
|
|
80
|
-
|
|
207
|
+
1. project config: `.pi/jarvis.json`
|
|
208
|
+
2. global config: `~/.pi/agent/extensions/pi-jarvis.json` or the equivalent path under a custom Pi agent dir
|
|
209
|
+
3. built-in defaults: model `follow-main`, thinking `auto`
|
|
81
210
|
|
|
82
|
-
|
|
211
|
+
---
|
|
83
212
|
|
|
84
|
-
|
|
85
|
-
When enabled, `/jarvis` may use local:
|
|
213
|
+
## Overlay controls
|
|
86
214
|
|
|
87
|
-
|
|
88
|
-
- `bash`
|
|
89
|
-
- `edit`
|
|
90
|
-
- `write`
|
|
91
|
-
- `mcp` when the MCP adapter is available in the current Pi environment
|
|
215
|
+
The overlay header exposes three controls, all **off by default**:
|
|
92
216
|
|
|
93
|
-
|
|
217
|
+
| Control | What it does | Safety model |
|
|
218
|
+
|---|---|---|
|
|
219
|
+
| `Repo tools` | Enables local `read`, `bash`, `edit`, `write`, and optional `mcp` | Explicit opt-in |
|
|
220
|
+
| `Note main` | Sends a concise, non-interrupting note to the main session | Explicit opt-in |
|
|
221
|
+
| `Redirect` | Sends a redirecting instruction to the main session | Explicit opt-in + per-send confirmation |
|
|
94
222
|
|
|
95
|
-
|
|
96
|
-
Allows `/jarvis` to send a concise, non-interrupting note back to the main session.
|
|
223
|
+
`Note main` and `Redirect` can be forcibly disabled when the active `/jarvis` model is incompatible with bridge tools.
|
|
97
224
|
|
|
98
|
-
###
|
|
99
|
-
Allows `/jarvis` to send a redirecting instruction to the main session, but every actual redirect still requires explicit confirmation.
|
|
225
|
+
### Permission flow
|
|
100
226
|
|
|
101
|
-
|
|
227
|
+
```mermaid
|
|
228
|
+
flowchart TD
|
|
229
|
+
A[Overlay opens] --> B[Repo tools off]
|
|
230
|
+
A --> C[Note main off]
|
|
231
|
+
A --> D[Redirect off]
|
|
232
|
+
|
|
233
|
+
B -->|enable| E[Jarvis may use local tools]
|
|
234
|
+
E --> F{MCP adapter available?}
|
|
235
|
+
F -->|yes| G[Local tools + MCP]
|
|
236
|
+
F -->|no| H[Local tools only]
|
|
237
|
+
|
|
238
|
+
C -->|enable| I[Jarvis may send a quiet note to main]
|
|
239
|
+
D -->|enable| J[Jarvis may request redirect sends]
|
|
240
|
+
J --> K[Every redirect still requires confirmation]
|
|
241
|
+
|
|
242
|
+
L[Incompatible /jarvis model] --> M[Note main disabled]
|
|
243
|
+
L --> N[Redirect disabled]
|
|
244
|
+
```
|
|
245
|
+
|
|
246
|
+
---
|
|
247
|
+
|
|
248
|
+
## Redirect flow
|
|
249
|
+
|
|
250
|
+
```mermaid
|
|
251
|
+
sequenceDiagram
|
|
252
|
+
participant You
|
|
253
|
+
participant Jarvis
|
|
254
|
+
participant Main as Main session
|
|
255
|
+
|
|
256
|
+
You->>Jarvis: Enable Redirect
|
|
257
|
+
You->>Jarvis: "Tell the main session to stop and inspect overlay teardown"
|
|
258
|
+
Jarvis->>You: Confirmation request
|
|
259
|
+
You-->>Jarvis: Approve
|
|
260
|
+
Jarvis-->>Main: Redirect instruction
|
|
261
|
+
Main-->>You: Continues on new priority
|
|
262
|
+
```
|
|
263
|
+
|
|
264
|
+
---
|
|
265
|
+
|
|
266
|
+
## Session behavior
|
|
102
267
|
|
|
103
268
|
- `/jarvis` keeps its own isolated conversation state
|
|
104
269
|
- prior side-session history is restored from a session file under `jarvis-sessions/`
|
|
105
|
-
-
|
|
106
|
-
-
|
|
270
|
+
- Jarvis sees current main-session state plus a compact delta since the last `/jarvis` turn
|
|
271
|
+
- `/compact`, `/tree`, and `/new` entered inside `/jarvis` operate on the side-session, not the main session
|
|
272
|
+
- plain `/jarvis-model <provider/model>` writes the project model override; use `--global` to change the global default
|
|
273
|
+
- plain `/jarvis-thinking <level>` writes the project thinking override; use `--global` to change the global default
|
|
274
|
+
- thinking-step streaming is intentionally collapsed to a cleaner animated fallback for readability
|
|
275
|
+
|
|
276
|
+
---
|
|
277
|
+
|
|
278
|
+
## Example usage
|
|
279
|
+
|
|
280
|
+
### Ask for live status
|
|
281
|
+
|
|
282
|
+
```bash
|
|
283
|
+
/jarvis what is the main agent doing right now?
|
|
284
|
+
```
|
|
285
|
+
|
|
286
|
+
### Ask for triage while the main lane keeps moving
|
|
287
|
+
|
|
288
|
+
```bash
|
|
289
|
+
/jarvis summarize the last failing test and tell me the fastest likely fix
|
|
290
|
+
```
|
|
291
|
+
|
|
292
|
+
### Use Jarvis as a repo-side helper
|
|
293
|
+
|
|
294
|
+
```bash
|
|
295
|
+
/jarvis inspect overlay.ts for teardown or redraw risks
|
|
296
|
+
```
|
|
297
|
+
|
|
298
|
+
### Send a non-interrupting note back to the main session
|
|
299
|
+
|
|
300
|
+
1. Open `/jarvis`
|
|
301
|
+
2. Enable `Note main`
|
|
302
|
+
3. Ask Jarvis to send the note
|
|
303
|
+
|
|
304
|
+
### Send a redirect safely
|
|
305
|
+
|
|
306
|
+
1. Open `/jarvis`
|
|
307
|
+
2. Enable `Redirect`
|
|
308
|
+
3. Ask Jarvis to redirect the main session
|
|
309
|
+
4. Confirm the send
|
|
310
|
+
|
|
311
|
+
---
|
|
312
|
+
|
|
313
|
+
## Compatibility note
|
|
314
|
+
|
|
315
|
+
This repository's current validation baseline is **Pi 0.69.0**.
|
|
316
|
+
|
|
317
|
+
The package relies on Pi-provided peer dependencies, so treat other host versions as **not the validated baseline for this repo** unless you have tested them yourself.
|
|
318
|
+
|
|
319
|
+
---
|
|
107
320
|
|
|
108
321
|
## Development
|
|
109
322
|
|
|
@@ -131,15 +344,14 @@ Build the published package contents:
|
|
|
131
344
|
npm run build
|
|
132
345
|
```
|
|
133
346
|
|
|
134
|
-
|
|
347
|
+
Preview the npm payload:
|
|
135
348
|
|
|
136
|
-
|
|
349
|
+
```bash
|
|
350
|
+
npm pack --dry-run
|
|
351
|
+
```
|
|
137
352
|
|
|
138
|
-
|
|
139
|
-
- `README.md`
|
|
140
|
-
- `LICENSE`
|
|
141
|
-
- `package.json`
|
|
353
|
+
---
|
|
142
354
|
|
|
143
355
|
## License
|
|
144
356
|
|
|
145
|
-
MIT
|
|
357
|
+
`pi-jarvis` is released under the **MIT License**. See [LICENSE](./LICENSE).
|
package/dist/index.d.ts.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../index.ts"],"names":[],"mappings":"AAEA,OAAO,EAGN,KAAK,YAAY,EAGjB,MAAM,+BAA+B,CAAC;
|
|
1
|
+
{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../index.ts"],"names":[],"mappings":"AAEA,OAAO,EAGN,KAAK,YAAY,EAGjB,MAAM,+BAA+B,CAAC;AA8FvC,MAAM,CAAC,OAAO,UAAU,eAAe,CAAC,EAAE,EAAE,YAAY,GAAG,IAAI,CA6c9D"}
|