weml-monaco 0.11.0 → 0.11.1

package/CHANGELOG.md

@@ -8,6 +8,11 @@ This package shares the language logic of the VS Code extension (`weml-support`)
 entries below track the port catching up with its provider changes; since the shared language
 features, both take the same code.
 
+## [0.11.1] — 2026-10-15
+
+### Changed
+- The README is trimmed to what a user of the package needs.
+
 ## [0.11.0] — 2026-10-14
 
 ### Added

package/README.md

@@ -26,7 +26,7 @@ This package does **not** modify the original VS Code extension — it is a
 standalone re-implementation living entirely in this package (`packages/weml-monaco` of the
 monorepo).
 
-## Install & build
+## Install
 
 ```bash
 npm install weml-monaco
@@ -44,17 +44,6 @@ The package has no runtime dependencies (`node-html-parser`,
 | `weml-monaco/editor`   | `dist/editor.mjs`       | the editor and its workbench (below)   |
 | `weml-monaco/react`    | `dist/react.mjs`        | the editor as a React component        |
 
-Working on the package itself:
-
-```bash
-npm ci                 # at the repository root (npm workspaces)
-cd packages/weml-monaco
-npm run build          # tsup → dist/ (ESM + CJS + IIFE + declarations)
-npm run typecheck      # tsc --noEmit
-npm test               # build + Node smoke test
-npm run check:package  # publint + arethetypeswrong on the packed tarball
-```
-
 ## Usage
 
 Monaco is **passed in** at registration time, so this works no matter how
@@ -337,7 +326,7 @@ const panel = createWemlPanel(
 ## The WEML preview
 
 A live preview of the editor's document, rendered with
-[`weml-stylesheet`](../weml-stylesheet) — an **optional peer dependency**:
+[`weml-stylesheet`](https://github.com/Burjuy/weml-language-vscode-extension/tree/main/packages/weml-stylesheet) — an **optional peer dependency**:
 install it (and load its CSS) to use this entry; nothing else needs it.
 
 ```ts
@@ -434,25 +423,3 @@ in VS Code.
 The earlier flat DOM toolbar (`createWemlToolbar(monaco, editor, { container,
 onStatus })`) still works and still registers the editor actions, but it is
 deprecated in favour of the WEML panel and gets no new features.
-
-## Trying it out
-
-The monorepo's dev app, [`storybook/`](../../storybook) (`weml-storybook`)
-(`npm start -w weml-storybook` from the repository root), runs this package from
-its sources in a full editor: completions (Ctrl+Space), hover, "Format
-Document", the outline, diagnostics and the toolbar.
-
-## How it relates to the VS Code extension
-
-The language logic is shared with the VS Code extensions, not copied — two workspace packages,
-bundled into every build (neither is a runtime dependency):
-
-| shared (workspace package)           | adapted for Monaco                       |
-| ------------------------------------ | ---------------------------------------- |
-| `weml-language-core`: schema, structure rules, snippets, entities, markdown text, the language features (diagnostics, hover, completion, outline), tool model, wrap / renumber | `schema/docs.ts` (plain `IMarkdownString`) |
-| `weml-normalizer`: the canonical normalizer | `wemlDocument.ts` (parse cache, offsets ↔ Monaco positions), `providers/*` (the features' data → Monaco provider types), `index.ts` (registration + diagnostics) |
-
-The diagnostics, tooltips, suggestions and outline are computed once, in the shared package, as
-plain data with offsets — the VS Code extension and this package only map them to their editor's
-types, so both editors report the same problems and offer the same items. Parsing uses
-`vscode-html-languageservice` (editor-agnostic, runs in the browser and in the worker).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "weml-monaco",
-  "version": "0.11.0",
+  "version": "0.11.1",
   "description": "WEML (White Estate Markup Language) language support for the Monaco editor: syntax highlighting, autocomplete, hover docs, structure diagnostics, outline and canonical formatting.",
   "license": "MIT",
   "type": "commonjs",