@vmz/plugin-shiki 0.3.6 → 0.3.7

package/README.md

@@ -1,53 +1,53 @@
-# @vmz/plugin-shiki
-
-## Code examples that are part of the reading experience
-
-`@vmz/plugin-shiki` brings Shiki's high-quality syntax highlighting to VMZ applications. It is designed for guides, API
-reference, technical blogs, source browsers, tutorials, and any product surface where code is meant to be read
-carefully.
-
-## Why Shiki fits VMZ documents
-
-Code snippets should remain useful before a page becomes interactive. Shiki supports a content-first experience: source
-can be highlighted as part of the rendered document instead of relying on a browser-only code viewer to make a page
-readable.
-
-For VMZ examples, the plugin can share the same language presentation used by VMZ editor tooling. That consistency helps
-readers move from documentation to a real `.vmz` file without relearning the visual grammar.
-
-It is especially useful for:
-
-- product documentation that must be readable before interaction starts;
-- API and configuration references where source is the main content;
-- tutorials that move between prose and real VMZ components;
-- source browsers that need trustworthy language presentation.
-
-## Third-party TextMate grammar (VMZ-2)
-
-By default the runtime loads `vmz-textmate/shiki`. For other languages (e.g. VOS), pass a peer adapter:
-
-```ts
-import shiki from '@vmz/plugin-shiki';
-
-export default defineConfig({
-  plugins: [shiki({ textmate: '@game-gpt/vos-textmate/shiki' })],
-  engines: { code: 'shiki' },
-});
-```
-
-The plugin writes `dist/_vmz/plugin-shiki.config.json`; the runtime reads it in SSR (`VMZ_DIST`) and in the browser (`fetch`).
-
-## VMZ boundary
-
-Shiki owns source presentation. VMZ owns document structure, SSR, optional interaction, testing, and delivery. The
-plugin should make code easier to understand without becoming a parallel application runtime.
-
-## A content-first feature set 🎨
-
-- **Readable SSR:** highlighted source can arrive with the page instead of flashing into place later.
-- **VMZ consistency:** examples can share the grammar readers see in their editor.
-- **Theme-aware presentation:** technical content can belong to the surrounding design.
-- **Graceful fallback:** source remains readable when rich highlighting is unavailable.
-
-Use Shiki where code itself is part of the product. If users are meant to edit the code, pair the reading experience
-with CodeMirror or Monaco rather than stretching a highlighter into an editor.
+# @vmz/plugin-shiki
+
+## Code examples that are part of the reading experience
+
+`@vmz/plugin-shiki` brings Shiki's high-quality syntax highlighting to VMZ applications. It is designed for guides, API
+reference, technical blogs, source browsers, tutorials, and any product surface where code is meant to be read
+carefully.
+
+## Why Shiki fits VMZ documents
+
+Code snippets should remain useful before a page becomes interactive. Shiki supports a content-first experience: source
+can be highlighted as part of the rendered document instead of relying on a browser-only code viewer to make a page
+readable.
+
+For VMZ examples, the plugin can share the same language presentation used by VMZ editor tooling. That consistency helps
+readers move from documentation to a real `.vmz` file without relearning the visual grammar.
+
+It is especially useful for:
+
+- product documentation that must be readable before interaction starts;
+- API and configuration references where source is the main content;
+- tutorials that move between prose and real VMZ components;
+- source browsers that need trustworthy language presentation.
+
+## Third-party TextMate grammar (VMZ-2)
+
+By default the runtime loads `vmz-textmate/shiki`. For other languages (e.g. VOS), pass a peer adapter:
+
+```ts
+import shiki from '@vmz/plugin-shiki';
+
+export default defineConfig({
+  plugins: [shiki({ textmate: '@game-gpt/vos-textmate/shiki' })],
+  engines: { code: 'shiki' },
+});
+```
+
+The plugin writes `dist/_vmz/plugin-shiki.config.json`; the runtime reads it in SSR (`VMZ_DIST`) and in the browser (`fetch`).
+
+## VMZ boundary
+
+Shiki owns source presentation. VMZ owns document structure, SSR, optional interaction, testing, and delivery. The
+plugin should make code easier to understand without becoming a parallel application runtime.
+
+## A content-first feature set 🎨
+
+- **Readable SSR:** highlighted source can arrive with the page instead of flashing into place later.
+- **VMZ consistency:** examples can share the grammar readers see in their editor.
+- **Theme-aware presentation:** technical content can belong to the surrounding design.
+- **Graceful fallback:** source remains readable when rich highlighting is unavailable.
+
+Use Shiki where code itself is part of the product. If users are meant to edit the code, pair the reading experience
+with CodeMirror or Monaco rather than stretching a highlighter into an editor.

package/package.json

@@ -1,13 +1,16 @@
 {
   "dependencies": {
-    "@vmz/plugin": "0.3.6"
+    "@vmz/plugin": "0.3.7"
   },
   "description": "VMZ Shiki adapter - <Shiki> + code engine registration",
   "devDependencies": {
     "@types/node": "^22.15.0",
     "shiki": "^3.12.2",
     "typescript": "^5.8.3",
-    "vmz-textmate": "0.3.6"
+    "vmz-textmate": "0.3.7"
+  },
+  "engines": {
+    "node": ">=24.12.0"
   },
   "exports": {
     ".": {
@@ -58,5 +61,5 @@
   },
   "type": "module",
   "types": "./dist/vmz.plugin.d.ts",
-  "version": "0.3.6"
+  "version": "0.3.7"
 }