@kungal/editor-nuxt 0.12.0 → 0.13.0

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # @kungal/editor-nuxt
 
+## 0.13.0
+
+### Minor Changes
+
+- 8ce8210: The Nuxt layer now preconfigures Vite's dev dependency optimizer, so consumers
+  never hit the micromark/`debug` dev error.
+
+  Under `nuxt dev`, Milkdown's tokenizer (micromark) resolves to its DEV build,
+  which does `import debug from 'debug'`. `debug` is CommonJS; unless Vite
+  pre-bundles it, its browser build is served raw with no `default` export and the
+  editor throws at load — `SyntaxError: 'debug' does not provide an export named
+'default'` (create-tokenizer.js), which also aborts app init. Whether it fires is
+  non-deterministic per app (it depends on whether Vite's dep scan reaches the
+  editor before it evaluates).
+
+  The layer now sets `vite.optimizeDeps.include` for the editor + Milkdown entry
+  points, which Nuxt merges into every consuming app — so esbuild pre-bundles that
+  subgraph and resolves micromark's CJS `debug` inside the bundle. No app needs to
+  configure this itself. Dev-only: the production build strips micromark's debug
+  calls, so `nuxt build` is unaffected. (Plain non-Nuxt Vite apps that use
+  `@kungal/editor-vue` directly still add the same `optimizeDeps.include` manually —
+  a layer can inject Vite config, a plain package cannot.)
+
+### Patch Changes
+
+- @kungal/editor-core@0.13.0
+- @kungal/editor-vue@0.13.0
+
 ## 0.12.0
 
 ### Minor Changes

package/nuxt.config.ts

@@ -26,7 +26,36 @@ export default defineNuxtConfig({
         })
       }
     })
-  ]
+  ],
+
+  // Under `nuxt dev`, Milkdown's markdown tokenizer (micromark) resolves to its
+  // DEV build, which does `import debug from 'debug'`. `debug` is CommonJS, so
+  // unless Vite pre-bundles it, its browser.js is served raw with no `default`
+  // export and the editor throws at load:
+  //   SyntaxError: … 'debug' does not provide an export named 'default'
+  //   (create-tokenizer.js)
+  // which also aborts app init. Whether it fires is non-deterministic per app —
+  // it depends on whether Vite's dep scan reaches the editor before it evaluates
+  // (the docs happens to get auto-scanned; other consumers don't). So pin it
+  // HERE, in the layer: force-including the editor/milkdown ENTRY points makes
+  // esbuild pre-bundle their whole subgraph and resolve micromark's CJS `debug`
+  // INSIDE the bundle. Merged into every consumer that extends this layer, so no
+  // app configures it. Dev-only: the prod build strips micromark's debug calls.
+  //
+  // NB: include the resolvable ENTRY points, not `'debug'` — under pnpm's
+  // non-hoisted layout `debug` isn't resolvable from the app root, so Vite would
+  // silently skip it. Unresolvable entries below are skipped too (harmless).
+  vite: {
+    optimizeDeps: {
+      include: [
+        '@kungal/editor-vue',
+        '@kungal/editor-core',
+        '@kungal/editor-core/preset',
+        '@milkdown/kit/preset/commonmark',
+        '@milkdown/kit/preset/gfm'
+      ]
+    }
+  }
 })
 
 // NOTE: this layer does NOT own a Tailwind entry or import editor styles. The

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kungal/editor-nuxt",
-  "version": "0.12.0",
+  "version": "0.13.0",
   "description": "KunEditor Nuxt Layer — wraps @kungal/editor-vue and auto-imports <KunEditor> so an existing Nuxt app keeps its exact DX (no import needed).",
   "type": "module",
   "keywords": [
@@ -30,8 +30,8 @@
     "nuxt.config.ts"
   ],
   "dependencies": {
-    "@kungal/editor-core": "0.12.0",
-    "@kungal/editor-vue": "0.12.0"
+    "@kungal/editor-core": "0.13.0",
+    "@kungal/editor-vue": "0.13.0"
   },
   "peerDependencies": {
     "@kungal/ui-vue": "^2.7.0",