@nseng-ai/ns 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 +28 -0
- package/bin/ns.js +647 -250
- package/kernel/cli.js +7494 -0
- package/kernel/command-io.js +139 -0
- package/kernel/context.js +4068 -0
- package/kernel/pi-text-generation.js +120 -0
- package/kernel/sdk.js +157 -0
- package/package.json +12 -1
package/README.md
CHANGED
|
@@ -3,3 +3,31 @@
|
|
|
3
3
|
Checkout-free npm package for the `ns` CLI.
|
|
4
4
|
|
|
5
5
|
The published package bin points at prebuilt JavaScript (`bin/ns.js`) assembled by the package preparation step. Developer source-checkout shims remain separate from this npm package boundary.
|
|
6
|
+
|
|
7
|
+
The package also owns the public kernel subpaths for checkout-free consumers:
|
|
8
|
+
|
|
9
|
+
- `@nseng-ai/ns/kernel/cli`
|
|
10
|
+
- `@nseng-ai/ns/kernel/command-io`
|
|
11
|
+
- `@nseng-ai/ns/kernel/context`
|
|
12
|
+
- `@nseng-ai/ns/kernel/pi-text-generation`
|
|
13
|
+
- `@nseng-ai/ns/kernel/sdk`
|
|
14
|
+
|
|
15
|
+
The standalone workspace `@nseng-ai/kernel` package remains private and is folded into these `@nseng-ai/ns` subpaths at package-preparation time.
|
|
16
|
+
|
|
17
|
+
## Release preparation for `0.1.1`
|
|
18
|
+
|
|
19
|
+
`@nseng-ai/ns@0.1.1` is the publishable patch target for registry-visible kernel subpath metadata. Local release qualification should run:
|
|
20
|
+
|
|
21
|
+
```sh
|
|
22
|
+
pnpm --dir ts --filter @nseng-ai/ns run publish:dry-run
|
|
23
|
+
pnpm --dir ts --filter @nseng-ai/ns run pack:local
|
|
24
|
+
pnpm --dir ts --filter @nseng-ai/ns run smoke:checkout-free
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
The generated `dist/publish/package.json` must keep `bin.ns` at `bin/ns.js`, expose the five `./kernel/*` exports above as `./kernel/*.js`, and include `publishConfig.access = "public"`.
|
|
28
|
+
|
|
29
|
+
Actual publication is a separate authorized step; do not publish as part of local qualification. After an authorized publish, verify the registry metadata with:
|
|
30
|
+
|
|
31
|
+
```sh
|
|
32
|
+
npm view @nseng-ai/ns@0.1.1 name version bin exports dist.tarball time --json
|
|
33
|
+
```
|