@bacnh85/pi-serena 0.1.0 → 0.1.1
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/README.md +8 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -6,6 +6,12 @@ Note: Serena itself is a Python package. The TypeScript worker owns lifecycle, r
|
|
|
6
6
|
|
|
7
7
|
## Install
|
|
8
8
|
|
|
9
|
+
Install the published package from npm:
|
|
10
|
+
|
|
11
|
+
```bash
|
|
12
|
+
pi install npm:@bacnh85/pi-serena
|
|
13
|
+
```
|
|
14
|
+
|
|
9
15
|
From this repository checkout, install only this extension package:
|
|
10
16
|
|
|
11
17
|
```bash
|
|
@@ -18,6 +24,8 @@ For local development from a checkout:
|
|
|
18
24
|
pi -e ./extensions/pi-serena
|
|
19
25
|
```
|
|
20
26
|
|
|
27
|
+
The package manifest points Pi directly at `./index.ts`, so published npm installs and local installs load the same extension entrypoint.
|
|
28
|
+
|
|
21
29
|
There is intentionally no repository-level Pi package. Install each extension from its own subdirectory, matching `extensions/pi-rtk` and future extensions.
|
|
22
30
|
|
|
23
31
|
After install or update, restart Pi or run `/reload` in an existing Pi session.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@bacnh85/pi-serena",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"description": "Pi extension that provides Serena semantic code tools through a persistent worker.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"publishConfig": {
|
|
@@ -28,7 +28,7 @@
|
|
|
28
28
|
],
|
|
29
29
|
"pi": {
|
|
30
30
|
"extensions": [
|
|
31
|
-
"."
|
|
31
|
+
"./index.ts"
|
|
32
32
|
]
|
|
33
33
|
},
|
|
34
34
|
"peerDependencies": {
|