dsh-plugin-toolkit 0.8.0 → 0.8.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/CHANGELOG.md CHANGED
@@ -1,3 +1,15 @@
1
+ ## 0.8.1
2
+
3
+ `0.8.0` installed and then did nothing: the loader starts a plugin by importing
4
+ the bare package name, and `exports["."]` still pointed at the CLI, so the row
5
+ had no `apply` to run.
6
+
7
+ - `exports["."]` is `./index.js`; the CLI keeps `./cli` and `bin`, the testkit
8
+ keeps `./testkit`.
9
+ - `test/entry.test.mjs` guards the shape: the root export is the plugin, the
10
+ patch file names the package once as `- insert:`, and every path
11
+ `package.json` points at is in `files`.
12
+
1
13
  ## 0.8.0
2
14
 
3
15
  The toolkit can now be installed as a plugin, because a tool that cannot be
package/README.md CHANGED
@@ -18,6 +18,15 @@ npx dsh-plugin-toolkit@0.7.0 release --pr --merge # tag, wait for n
18
18
  | changing a panel that is already installed | [`dev`](#2-develop-a-panel) | `mount`, the testkit |
19
19
  | shipping a version | [`verify`](#3-ship-a-version) | `release`, `index` |
20
20
 
21
+ It also installs as a plugin. `dsh plugin add dsh-plugin-toolkit` adds a
22
+ **Plugin doctor** tab to the right sidebar: name the folder that holds a
23
+ plugin's `package.json`, and it runs the same checks `verify` runs and lists
24
+ what would fail — the same answers as the CLI, without leaving the app.
25
+
26
+ ```
27
+ $ dsh plugin add dsh-plugin-toolkit
28
+ ```
29
+
21
30
  ### 1. Write a plugin
22
31
 
23
32
  [`init`](#start-from-a-plugin-that-already-passes) writes the files whose absence shows up as a failed first publish — `engines.dsh`, the patch file, a `files` list that ships the code, a client bundle, a test for it, and the CI that runs both. `doctor` then checks the same things without writing anything, and [`verify`](#prove-the-tarball-works-not-just-the-repository) checks the tarball instead of the working copy.
package/package.json CHANGED
@@ -1,13 +1,14 @@
1
1
  {
2
2
  "name": "dsh-plugin-toolkit",
3
- "version": "0.8.0",
3
+ "version": "0.8.1",
4
4
  "description": "Preflight, release and test DeepSeek Harness plugins: checks what the host needs, waits for npm to actually serve the version, and keeps the market index honest.",
5
5
  "type": "module",
6
6
  "bin": {
7
7
  "dsh-plugin": "bin/dsh-plugin.mjs"
8
8
  },
9
9
  "exports": {
10
- ".": "./lib/cli.mjs",
10
+ ".": "./index.js",
11
+ "./cli": "./lib/cli.mjs",
11
12
  "./testkit": "./lib/testkit/index.mjs"
12
13
  },
13
14
  "files": [
@@ -74,5 +75,6 @@
74
75
  "bundle": {
75
76
  "patch": "./cordis.patch.yml"
76
77
  }
77
- }
78
+ },
79
+ "main": "index.js"
78
80
  }