@theokit/sdk 4.63.3 → 4.63.4-next.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/CHANGELOG.md +21 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,26 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 4.63.4-next.0
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 01630ec: The README explains that three unrelated things in this ecosystem are called "plugin", and that
|
|
8
|
+
two of them share one option.
|
|
9
|
+
|
|
10
|
+
A **framework plugin** (`@theokit/plugin-canvas`, `@theokit/auth-github`, …) extends a `theokit`
|
|
11
|
+
application — routes, UI, devtools, CLI verbs. An **SDK code plugin** (`PermissionPlugin.create(…)`,
|
|
12
|
+
`Handoff.asPlugin(…)`) extends an agent and is passed as `Agent.create({ plugins: [ … ] })`. The
|
|
13
|
+
same option also accepts `{ enabled: ["name"] }`, which selects **file-discovered** plugins under
|
|
14
|
+
`.theokit/plugins/` and is mutually exclusive with the array form.
|
|
15
|
+
|
|
16
|
+
Reaching for the wrong one raises no error; it simply has no effect. Installing `plugin-payments`
|
|
17
|
+
does nothing for an agent, and passing `PermissionPlugin` does nothing for a route.
|
|
18
|
+
|
|
19
|
+
It also records the observation that sends people looking for a bug that is not there:
|
|
20
|
+
`agent.pluginsManager` only ever holds the file-discovered form, so it reports `plugins: []` while
|
|
21
|
+
a code plugin is registered and working. An empty manager beside a populated `options.plugins` is
|
|
22
|
+
the normal shape.
|
|
23
|
+
|
|
3
24
|
## 4.63.3
|
|
4
25
|
|
|
5
26
|
### Patch Changes
|
package/package.json
CHANGED