hono-decks 1.2.0 → 1.2.2

package/README.ja.md

@@ -9,7 +9,7 @@ Hono と Cloudflare Workers 上で MDX のスライドを配信するための
 既存のアプリに `hono-decks` をインストールし、構成に合わせて初期設定します。
 
 ```sh
-npm install hono-decks
+npm install hono-decks@latest
 
 # Hono＋Vite
 npx hono-decks init --framework hono
@@ -22,6 +22,8 @@ npm run dev
 npm run build
 ```
 
+新規導入では`@latest`で現在の公開版を選びます。同じ環境を再現する場合は、動作確認したバージョンを明示してください。
+
 どちらも、既存の Vite 設定を保持して自動コンパイルを登録し、
 `hono-decks.config.ts`、`src/decks.ts`、サンプルの
 `decks/welcome/deck.mdx` を作ります。生成ファイルがない状態からでも
@@ -69,8 +71,9 @@ npm run dev
 npm run build
 ```
 
-この連携には `void-plugin-hono-jsx@^0.5.0` の standalone compiler／client export
-が必要です。`--install` は対応範囲のアダプターを選びます。
+この連携には standalone compiler／client export を持つアダプターが必要です。
+新規インストールの既定値は `void-plugin-hono-jsx@^0.6.0` です。
+`--install` は、インストール済みの互換アダプターを維持します。
 `--install` を省略する場合は、Markdown 用の任意 peer も必要です：
 `markdown-exit@^1.3.0 yaml@^2.9.1 markdown-it-container@^4.0.0 shiki@^4.5.0 @shikijs/transformers@^4.5.0`。
 動作確認した組み合わせは Void 1.1.11、Vite 8.3.4、Hono 4.13.13 です。

package/README.md

@@ -9,7 +9,7 @@ hono-decks serves MDX slide decks from Hono applications and Cloudflare Workers.
 Install hono-decks in an existing app and choose its integration:
 
 ~~~sh
-npm install hono-decks
+npm install hono-decks@latest
 
 # Hono + Vite
 npx hono-decks init --framework hono
@@ -22,6 +22,8 @@ npm run dev
 npm run build
 ~~~
 
+For a new app, `@latest` selects the current published release. To reproduce a setup, replace it with the exact version you have verified.
+
 Both modes preserve the existing Vite config while adding automatic compilation,
 create `hono-decks.config.ts`, `src/decks.ts`, and a sample
 `decks/welcome/deck.mdx`. Generated code stays in Vite virtual modules and is not written to disk.
@@ -68,9 +70,9 @@ npm run dev
 npm run build
 ~~~
 
-This integration requires `void-plugin-hono-jsx@^0.5.0` or a compatible adapter
-with the `/markdown/compiler` and `/markdown/client` exports. `--install` selects
-the supported adapter range. Without `--install`, also install the optional Markdown peers:
+This integration requires an adapter with the `/markdown/compiler` and
+`/markdown/client` exports. New installations default to `void-plugin-hono-jsx@^0.6.0`;
+`--install` preserves an already installed compatible adapter. Without `--install`, also install the optional Markdown peers:
 `markdown-exit@^1.3.0 yaml@^2.9.1 markdown-it-container@^4.0.0 shiki@^4.5.0 @shikijs/transformers@^4.5.0`.
 The verified host versions are Void 1.1.11, Vite 8.3.4, and Hono 4.13.13.
 
@@ -465,7 +467,7 @@ At this level, the application owns the mount path, source policy, and option me
 ## Void Hono Markdown
 
 Set `build.markdown: "void"` in `hono-decks.config.ts` to opt into `.md` decks
-alongside MDX. This requires `void-plugin-hono-jsx@^0.5.0` with its standalone compiler and client exports.
+alongside MDX. This requires `void-plugin-hono-jsx@^0.6.0` with its standalone compiler and client exports.
 See the [Void consumer fixture](https://github.com/ts-76/hono-decks/tree/main/fixtures/void-markdown)
 for package verification, Void middleware hosting, supported syntax and limitations.
 

package/dist/bin.js

@@ -2350,7 +2350,7 @@ async function runInitCommand(input, args, stdout, stderr) {
 		return { exitCode: 1 };
 	}
 	if (parsed.options.framework) try {
-		const { initializeVite } = await import("./init-vite-EA_L4k2H.js");
+		const { initializeVite } = await import("./init-vite-F2gLT72s.js");
 		const sampleSlug = await initializeVite(input.cwd, parsed.options.framework, parsed.options.configFile, parsed.options.entry, parsed.options.install ? { adapter: parsed.options.adapter } : void 0);
 		stdout(`Initialized ${parsed.options.framework} decks at /slides/${sampleSlug}. Run your usual dev or build command; no manual compile is needed.`);
 		return { exitCode: 0 };

package/dist/cli.js

@@ -2349,7 +2349,7 @@ async function runInitCommand(input, args, stdout, stderr) {
 		return { exitCode: 1 };
 	}
 	if (parsed.options.framework) try {
-		const { initializeVite } = await import("./init-vite-EA_L4k2H.js");
+		const { initializeVite } = await import("./init-vite-F2gLT72s.js");
 		const sampleSlug = await initializeVite(input.cwd, parsed.options.framework, parsed.options.configFile, parsed.options.entry, parsed.options.install ? { adapter: parsed.options.adapter } : void 0);
 		stdout(`Initialized ${parsed.options.framework} decks at /slides/${sampleSlug}. Run your usual dev or build command; no manual compile is needed.`);
 		return { exitCode: 0 };

package/dist/{init-vite-EA_L4k2H.js → init-vite-F2gLT72s.js}

@@ -81,7 +81,7 @@ async function installVoidDependencies(cwd, options = {}) {
 		specs.push(`hono-decks@${requested}`);
 	}
 	if (options.adapter || missing("void-plugin-hono-jsx/markdown/compiler")) {
-		let adapter = options.adapter ?? "void-plugin-hono-jsx@^0.5.0";
+		let adapter = options.adapter ?? "void-plugin-hono-jsx@^0.6.0";
 		if (/^\d+\./.test(adapter)) adapter = "void-plugin-hono-jsx@" + adapter;
 		else if (modernYarn && (adapter.endsWith(".tgz") || adapter.startsWith("file:"))) adapter = "void-plugin-hono-jsx@file:" + resolve(cwd, adapter.replace(/^file:/, ""));
 		specs.push(adapter);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hono-decks",
-  "version": "1.2.0",
+  "version": "1.2.2",
   "description": "Slide decks for Hono and Cloudflare Workers",
   "keywords": [
     "cloudflare-workers",

package/skills/hono-decks/references/getting-started.md

@@ -22,7 +22,7 @@ for manual integration and non-Vite applications.
 
 For an existing Void app, use `npx hono-decks init --framework void` after
 installing the compatible packages and Markdown peers described in the README.
-Use `void-plugin-hono-jsx@^0.4.0` for its standalone compiler and client exports. Init connects the existing Vite config, creates the routing
+Use `void-plugin-hono-jsx@^0.6.0` for its standalone compiler and client exports. Init connects the existing Vite config, creates the routing
 middleware and a sample `.md` deck at `/slides/welcome`, and uses virtual modules without generated
 files. Use the app's normal `dev` and `build` scripts without changes or a manual
 compile. Existing `.mdx` files remain supported. Unsupported configs or existing