@triggery/vite 0.1.1 → 0.1.2
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 +22 -0
- package/README.md +7 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,27 @@
|
|
|
1
1
|
# @triggery/vite
|
|
2
2
|
|
|
3
|
+
## 0.1.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- f23e155: Filled out the quick-start sections in the npm package READMEs that adopters land on first.
|
|
8
|
+
|
|
9
|
+
- `@triggery/core` README now contains a three-tab quick-start (React / Solid / Vue) with concrete `pnpm add` commands and runnable code, plus pointers to the per-binding README for the full walkthrough.
|
|
10
|
+
- `@triggery/react` README — was a stub. Now has the full four-file scenario (trigger + provider + Chat + Toast) ready to copy-paste, exactly mirroring the Solid and Vue examples.
|
|
11
|
+
|
|
12
|
+
Linked-bundle bump so the binding READMEs stay aligned with the core release; no code or API changes.
|
|
13
|
+
|
|
14
|
+
- 3385f5b: Every package README now ends with a tailored **Related packages** section and a consistent `## License` footer.
|
|
15
|
+
|
|
16
|
+
- Adapter packages (`zustand`, `redux`, `jotai`, `mobx`, `reatom`, `signals`, `query`) link to `core` + `react` (required peers) plus 2-3 alternative adapters so adopters can swap them out without re-reading the whole repo.
|
|
17
|
+
- Event-source packages (`dom`, `socket`) cross-link.
|
|
18
|
+
- DevTools packages (`devtools-redux`, `devtools-panel`, `devtools-bridge`) cross-link.
|
|
19
|
+
- Tooling packages (`eslint-plugin`, `codemod`, `cli`) cross-link.
|
|
20
|
+
- Bindings (`react`, `solid`, `vue`) link to each other so users mid-migration know there's a sibling with the same hook API.
|
|
21
|
+
- `@triggery/core/src/index.ts` JSDoc header had stale wording ("orchestration runtime for React business logic") — replaced with framework-agnostic phrasing matching the README.
|
|
22
|
+
|
|
23
|
+
No code or API changes. Drop-in patch.
|
|
24
|
+
|
|
3
25
|
## 0.1.1
|
|
4
26
|
|
|
5
27
|
### Patch Changes
|
package/README.md
CHANGED
|
@@ -40,6 +40,13 @@ That's it — every file matching the glob is auto-imported, so its top-level `c
|
|
|
40
40
|
* Editing an existing trigger file just re-runs its `createTrigger(...)` — the runtime's last-mount-wins replaces the old registration. No special handling needed.
|
|
41
41
|
* Adding / removing / renaming a trigger file invalidates the virtual module so its import list is rebuilt on the next request.
|
|
42
42
|
|
|
43
|
+
## Related packages
|
|
44
|
+
|
|
45
|
+
- [`@triggery/core`](https://www.npmjs.com/package/@triggery/core) — Required peer — runtime where discovered triggers register.
|
|
46
|
+
- [`@triggery/react`](https://www.npmjs.com/package/@triggery/react) — Most common combination with this plugin.
|
|
47
|
+
|
|
48
|
+
See the [full package list](https://github.com/triggeryjs/triggery#packages) in the repo README.
|
|
49
|
+
|
|
43
50
|
## License
|
|
44
51
|
|
|
45
52
|
MIT © Aleksey Skhomenko
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@triggery/vite",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
4
4
|
"description": "Vite plugin for Triggery — auto-imports every *.trigger.ts via a virtual module + HMR. Framework-agnostic (works alongside React, Solid, Vue).",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": "Aleksey Skhomenko",
|