weml-monaco 0.4.4 → 0.5.0

package/CHANGELOG.md

@@ -8,6 +8,36 @@ This package mirrors the language logic of the VS Code extension; entries below
 track the port catching up with the VS Code provider changes (see the root
 `CHANGELOG.md` for the extension).
 
+## [0.5.0] — 2026-09-09
+
+### Changed
+- **Breaking:** the Monaco type surface is imported from
+  `monaco-editor/editor/editor.api.js` instead of the `monaco-editor` root.
+  The root re-exports the TypeScript, CSS, JSON and HTML language
+  contributions, so its type forced every consumer to import Monaco whole and
+  ship all four language workers — around 11 MB of bundle nobody used. The
+  editor core carries everything this package actually touches. Passing the
+  full `monaco-editor` namespace still type-checks, since it is a superset.
+- **Breaking:** `peerDependencies.monaco-editor` raised from `>=0.34.0` to
+  `>=0.56.0`. The subpath resolves through the `exports` map introduced in
+  0.56 (`"./*": "./esm/vs/*.js"`) and needs `moduleResolution` `node16` or
+  `bundler`; on 0.55 and older the equivalent path was
+  `monaco-editor/esm/vs/editor/editor.api`.
+- Development and the CDN demo build against monaco-editor 0.56.
+
+### Fixed
+- The bundles no longer register themselves with an AMD loader. `he` (via
+  node-html-parser) ends in a UMD footer whose `define()` call is anonymous, so
+  loading `dist/index.global.js` from a `<script>` tag on a page that also runs
+  Monaco's AMD loader made the loader attribute that module to whatever it was
+  resolving, warning `Duplicate definition of module 'vs/editor/editor.main'`.
+  The build now folds `define.amd` to `false`, dropping the branch.
+
+The type-path change itself does not touch the runtime output: every Monaco
+import in `src/` is an `import type`, and only the first line of the emitted
+declarations changes. `dist/index.mjs`, `index.cjs` and `index.global.js`
+differ solely by the removed AMD footer above.
+
 ## [0.4.4] — 2026-09-07
 
 Synced with VS Code extension `0.7.12`.

package/README.md

@@ -58,7 +58,7 @@ Monaco is **passed in** at registration time, so this works no matter how
 Monaco itself is loaded (AMD/CDN, ESM bundle, or a global):
 
 ```ts
-import * as monaco from 'monaco-editor';
+import * as monaco from 'monaco-editor/editor/editor.api.js';
 import { registerWeml } from 'weml-monaco';
 
 const disposable = registerWeml(monaco);
@@ -69,6 +69,20 @@ monaco.editor.create(document.getElementById('container'), { model });
 // disposable.dispose();  // tears down every provider + diagnostics listener
 ```
 
+The import path is the editor core rather than the `monaco-editor` root on
+purpose. The root re-exports the TypeScript, CSS, JSON and HTML language
+contributions, so importing it pulls all four — and their workers — into the
+application bundle. `weml-monaco` never touches them: it only needs
+`editor`, `languages`, `Position`, `MarkerSeverity` and a handful of
+interfaces, all of which live in `editor/editor.api.js`. Passing the full
+`monaco-editor` namespace still type-checks (it is a superset), so this is a
+choice the consumer makes, not a restriction.
+
+The subpath resolves through the package's `exports` map, which requires
+**monaco-editor 0.56 or newer** and `moduleResolution` `node16`/`bundler`.
+On 0.55 and older the equivalent path was
+`monaco-editor/esm/vs/editor/editor.api`.
+
 `registerWeml(monaco, options?)` accepts:
 
 | option                 | default     | meaning                                            |

package/dist/index.cjs

@@ -267,7 +267,7 @@ var require_he = __commonJS({
         "escape": escape,
         "unescape": decode
       };
-      if (typeof define == "function" && typeof define.amd == "object" && define.amd) {
+      if (typeof define == "function" && false) {
         define(function() {
           return he;
         });