dsh-plugin-shop 0.8.3 → 0.8.4-beta.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/README.md CHANGED
@@ -122,7 +122,7 @@ bundle is not.
122
122
  | **Enable / disable** | Applies to an installed plugin without a restart. A plugin with a browser half also needs the open page reloaded, and the shop offers the button when it does |
123
123
  | **Installed state** | An installed plugin shows an Installed label on its card — or an Update button when the catalog has a newer version — plus an Uninstall button; the Installed filter in the category bar shows only installed plugins |
124
124
  | **Size & author** | Each card shows what installing the plugin puts on disk, next to the account that published it — npm's own unpacked figure, so it matches the package's npm page |
125
- | **Leave out what cannot run** | A plugin whose declared components your installation does not provide is badged incompatible; the filter at the end of the category bar takes those off the shelf. It never hides a plugin whose name is already taken by another install, and never subtracts from the Installed view — those cards are the only place the problem is explained or can be undone |
125
+ | **Leave out what cannot run** | A plugin whose required components your installation does not provide, or whose author declares a dsh version or profile other than the one you run, is badged incompatible; the filter at the end of the category bar takes those off the shelf. It never hides a plugin whose name is already taken by another install, and never subtracts from the Installed view — those cards are the only place the problem is explained or can be undone |
126
126
  | **Reload** | When an uninstall or a toggle is already live on the server and only the open page is stale, the shop offers to reload that page — never automatically, because a reload discards work in flight |
127
127
  | **Restart** | When the plugin's host half could not be brought up live — and also when it could, but the plugin has a browser half: a plugin that arrives mid-session reaches the page only through a restart, so the shop says so rather than offering a reload that would change nothing. It states the cost first: the page disconnects and in-flight work is interrupted |
128
128
  | **Self-update** | The shop shows its own version next to the search box, checks npm for a newer release, and updates itself with the pinned version — then the usual restart |
@@ -144,16 +144,19 @@ them are the reason the shelf is worth reading:
144
144
  dependencies, either of which would fail the install on your machine. A name a hair
145
145
  away from a popular one is held until someone clears it. Seventeen recorded
146
146
  reasons, all mechanical, and every rejection carries a line its author can read.
147
- 3. **Classify and record.** Seven categories, and the peer modules each plugin
148
- declares — names only, never version ranges.
147
+ 3. **Classify and record.** Seven categories, the peer modules each plugin
148
+ requires — names only, never version ranges — and the author's own
149
+ `dsh.compatibility`, when declared.
149
150
  4. **Publish.** Content-addressed JSON, to npm and GitHub Pages at once.
150
151
  5. **Fetch here.** This package races the origins and verifies the sha256 before
151
152
  trusting a byte.
152
- 6. **Check dependencies here too.** Your installation resolves each recorded peer name
153
- against *your* profile — the same question dsh's loader asks at mount time. A card
154
- whose modules are absent reads **Incompatible** and names them. That verdict is
155
- computed on your machine, because it depends on the harness you are actually
156
- running, not the one the build ran on.
153
+ 6. **Check dependencies here too.** Your installation looks up each recorded peer name
154
+ in *your* profile, then sets aside whatever dsh's web client provides itself. A card
155
+ whose modules neither provides reads **Incompatible** and names them, and so does
156
+ one whose author declares a dsh version or profile you are not running — it says
157
+ what was declared and what you run. That verdict is computed on your machine,
158
+ because it depends on the harness you are actually running, not the one the build
159
+ ran on.
157
160
 
158
161
  The full pipeline diagram lives in the
159
162
  [repository README](https://github.com/LivXue/dsh-plugin-shop#-how-it-fits-together).