@mercury-fw/kit 0.25.0

package/CHANGELOG.md

@@ -0,0 +1,8 @@
+# @mercury-fw/kit
+
+## 0.25.0
+
+### Patch Changes
+
+- @mercury-fw/plugin-types@0.25.0
+- @mercury-fw/channel-types@0.25.0

package/README.md

@@ -0,0 +1,7 @@
+# @mercury-fw/kit
+
+What a [Mercury](https://github.com/lucabro81/mercury-fw) plugin author imports: the contract a tool plugin implements (`Plugin`, `PLUGIN_API_VERSION` and the types around them) and the one a channel implements (`ChannelPlugin`, `CHANNEL_API_VERSION`), in one place. It carries no runtime, so a plugin that depends on it doesn't pull the framework in.
+
+A proper workflow for writing plugins, with an SDK on top of these contracts, is planned ([#27](https://github.com/lucabro81/mercury-fw/issues/27)).
+
+MIT

package/dist/index.d.ts

@@ -0,0 +1,17 @@
+/**
+ * The plugin-authoring surface — one entry a plugin author imports from, instead
+ * of reaching into the individual contract packages. It re-exports the two
+ * contracts a plugin is written against: the tool-plugin contract
+ * (`@mercury-fw/plugin-types`) and the channel-plugin contract
+ * (`@mercury-fw/channel-types`).
+ *
+ * This is Mercury's `@nuxt/kit` equivalent, deliberately thin for now: today it
+ * is a pure re-export of the contracts. The richer plugin-tool SDK (#27) — the
+ * helpers for building a tool without hand-wiring the runtime context — will
+ * land here, so authors depend on one stable entry as it grows.
+ *
+ * Split of concern: `@mercury-fw/core` is what an *app* consumes to run an
+ * instance; `@mercury-fw/kit` is what a plugin *author* consumes to write one.
+ */
+export * from "@mercury-fw/plugin-types";
+export * from "@mercury-fw/channel-types";

package/index.ts

@@ -0,0 +1,17 @@
+/**
+ * The plugin-authoring surface — one entry a plugin author imports from, instead
+ * of reaching into the individual contract packages. It re-exports the two
+ * contracts a plugin is written against: the tool-plugin contract
+ * (`@mercury-fw/plugin-types`) and the channel-plugin contract
+ * (`@mercury-fw/channel-types`).
+ *
+ * This is Mercury's `@nuxt/kit` equivalent, deliberately thin for now: today it
+ * is a pure re-export of the contracts. The richer plugin-tool SDK (#27) — the
+ * helpers for building a tool without hand-wiring the runtime context — will
+ * land here, so authors depend on one stable entry as it grows.
+ *
+ * Split of concern: `@mercury-fw/core` is what an *app* consumes to run an
+ * instance; `@mercury-fw/kit` is what a plugin *author* consumes to write one.
+ */
+export * from "@mercury-fw/plugin-types";
+export * from "@mercury-fw/channel-types";

package/package.json

@@ -0,0 +1,38 @@
+{
+  "name": "@mercury-fw/kit",
+  "version": "0.25.0",
+  "type": "module",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/lucabro81/mercury-fw.git",
+    "directory": "packages/libs/kit"
+  },
+  "files": [
+    "*.ts",
+    "dist",
+    "CHANGELOG.md"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "exports": {
+    ".": {
+      "mercury-fw-source": "./index.ts",
+      "types": "./dist/index.d.ts",
+      "default": "./index.ts"
+    }
+  },
+  "scripts": {
+    "typecheck": "tsc --noEmit"
+  },
+  "dependencies": {
+    "@mercury-fw/channel-types": "0.25.0",
+    "@mercury-fw/plugin-types": "0.25.0"
+  },
+  "devDependencies": {
+    "@mercury-fw/typescript-config": "*",
+    "@types/bun": "^1.4.0",
+    "typescript": "^6.0.3"
+  }
+}