@liminis/editor 0.7.0 → 0.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@liminis/editor",
3
- "version": "0.7.0",
3
+ "version": "0.8.0",
4
4
  "//publishing": "Publishing is deliberate, never incidental. `private: true` was this package's guard until verveguy/liminis-editor#39 took the publish decision; it is gone because that decision was taken, not because it was tidied away. The guard is now `prepublishOnly` -> scripts/guard-publish.mjs, which refuses unless LIMINIS_ALLOW_PUBLISH=1 is set explicitly. That variable is set at step scope in .github/workflows/publish.yml and nowhere else, so a release is the only path that publishes. Note that `npm publish --dry-run` does NOT report a private package as blocked (npm 10.8.2), which is why the guard is a script rather than a flag.",
5
5
  "license": "MIT",
6
6
  "description": "Lexical-based markdown WYSIWYG editor with mdast round-trip and a host-injection seam",
@@ -81,38 +81,38 @@
81
81
  "build:examples": "node scripts/build-examples.mjs",
82
82
  "build:site": "node scripts/build-site.mjs"
83
83
  },
84
- "//peerDependencies": "Ranges are the compatibility contract, not the tested matrix. CI resolves one point version per range (currently react 19.3.x latest and lexical 0.52.x latest), so every caret range here has an untested lower half — narrowing `react` to the devDependency's `^19.3.0` would not change that, it would only reject working consumers. The react floor is not a claim, it is enforced: `tests/package-manifest-contract.test.ts` (\"imports no React API newer than the declared 19.2.0 peer floor\") scans every source file for post-19.0 named imports — `useEffectEvent`, `Activity`, `cacheSignal`, `ViewTransition`, `captureOwnerStack` — and fails if one appears. Reaching for a newer API therefore breaks CI until you raise the floor here too, which is the pairing this note would otherwise only assert. Raise a floor when the code actually starts needing a later API, not to mirror whatever CI happened to install. This reasoning does not extend to the Lexical ranges below — see `//lexicalPeerPolicy`.",
84
+ "//peerDependencies": "Ranges are the compatibility contract, not the tested matrix. CI resolves one point version per range (currently react 19.3.x latest and lexical 0.53.x latest), so every caret range here has an untested lower half — narrowing `react` to the devDependency's `^19.3.0` would not change that, it would only reject working consumers. The react floor is not a claim, it is enforced: `tests/package-manifest-contract.test.ts` (\"imports no React API newer than the declared 19.2.0 peer floor\") scans every source file for post-19.0 named imports — `useEffectEvent`, `Activity`, `cacheSignal`, `ViewTransition`, `captureOwnerStack` — and fails if one appears. Reaching for a newer API therefore breaks CI until you raise the floor here too, which is the pairing this note would otherwise only assert. Raise a floor when the code actually starts needing a later API, not to mirror whatever CI happened to install. This reasoning does not extend to the Lexical ranges below — see `//lexicalPeerPolicy`.",
85
85
  "//lexicalPeerPolicy": "The twelve Lexical ranges are a single-caret bump per Lexical minor actually adopted and tested here, not a wide multi-version band. `react`'s untested lower half (above) is safe because a break there would be a bug in a stable major; Lexical is `0.x`, where every minor is permitted to break, so a wide band would claim compatibility with untested, potentially-breaking releases. Widening a range later is patch-safe; narrowing one is breaking — so this stays narrow by default and moves forward only when the code is actually run against the new minor. See docs/decisions/adr-92-lexical-peer-range-policy.md.",
86
86
  "peerDependencies": {
87
- "@lexical/code": "^0.52.0",
88
- "@lexical/code-prism": "^0.52.0",
89
- "@lexical/link": "^0.52.0",
90
- "@lexical/list": "^0.52.0",
91
- "@lexical/mark": "^0.52.0",
92
- "@lexical/markdown": "^0.52.0",
93
- "@lexical/react": "^0.52.0",
94
- "@lexical/rich-text": "^0.52.0",
95
- "@lexical/selection": "^0.52.0",
96
- "@lexical/table": "^0.52.0",
97
- "@lexical/utils": "^0.52.0",
98
- "lexical": "^0.52.0",
87
+ "@lexical/code": "^0.53.0",
88
+ "@lexical/code-prism": "^0.53.0",
89
+ "@lexical/link": "^0.53.0",
90
+ "@lexical/list": "^0.53.0",
91
+ "@lexical/mark": "^0.53.0",
92
+ "@lexical/markdown": "^0.53.0",
93
+ "@lexical/react": "^0.53.0",
94
+ "@lexical/rich-text": "^0.53.0",
95
+ "@lexical/selection": "^0.53.0",
96
+ "@lexical/table": "^0.53.0",
97
+ "@lexical/utils": "^0.53.0",
98
+ "lexical": "^0.53.0",
99
99
  "react": "^19.2.0",
100
100
  "react-dom": "^19.2.0"
101
101
  },
102
102
  "//mdast-util-to-markdown": "Pinned exactly, not a caret, and deliberately so. From 2.1.3 it leaves `_` unescaped when both neighbours are neither whitespace nor punctuation (`a_b`), and two places hand it a stand-in character instead of the real neighbour. (1) stringify.ts serialises a force-escaped character (#17) through a placeholder; that was private-use U+E004, which classifies as a word character, so an underscore typed next to a preserved escape went out bare and `a \\\\_b c_\\\\ d` re-parsed as emphasis. FIXED: the placeholder is now U+2BFF, a symbol, as the backslash it stands for is punctuation; the tests 'underscores beside force-escaped characters' in src/markdown/__tests__/stringify.test.ts cover it. (2) STILL OPEN: annotate mode splices sentinel tokens (U+E000-E003, annotate-sentinels.ts) into text, and those classify as word characters too, so a `_` at a mark boundary goes out bare where the plain export escapes it. That breaks the #970 invariant that annotate output differs from a plain export only by its tokens; fixtures 17-typed-underscore-after-inline-node and 17-escaped-backslash-then-underscore fail annotated-serialize-corpus.test.ts on 2.1.3+. Unlike the placeholder, a sentinel stands in for no character, so no fixed codepoint class is right. Move past 2.1.2 only once annotate mode keeps its tokens out of the library's view of neighbours and that suite passes.",
103
103
  "dependencies": {
104
- "@liminis/diagrams": "^0.1.6",
104
+ "@liminis/diagrams": "^0.2.2",
105
105
  "@mathjax/src": "^4.1.1",
106
- "lucide-react": "^1.49.0",
107
- "mdast-util-definition-list": "^2.0.0",
108
- "mdast-util-from-markdown": "^2.0.3",
106
+ "lucide-react": "^1.70.0",
107
+ "mdast-util-definition-list": "^2.0.1",
108
+ "mdast-util-from-markdown": "^2.1.0",
109
109
  "mdast-util-frontmatter": "^2.0.1",
110
110
  "mdast-util-gfm": "^3.1.0",
111
111
  "mdast-util-gfm-footnote": "^2.1.0",
112
112
  "mdast-util-math": "^3.0.0",
113
113
  "mdast-util-to-markdown": "2.1.2",
114
- "mermaid": "^12.0.0",
115
- "micromark-extension-definition-list": "^2.0.1",
114
+ "mermaid": "^12.3.0",
115
+ "micromark-extension-definition-list": "^2.0.2",
116
116
  "micromark-extension-frontmatter": "^2.0.0",
117
117
  "micromark-extension-gfm": "^3.0.0",
118
118
  "micromark-extension-gfm-footnote": "^2.1.0",
@@ -120,43 +120,43 @@
120
120
  "micromark-extension-wiki-link": "^0.0.4",
121
121
  "prismjs": "^1.30.0",
122
122
  "yaml": "^2.9.1",
123
- "zod": "^4.6.5",
124
- "zustand": "^5.0.12"
123
+ "zod": "^4.6.7",
124
+ "zustand": "^5.1.0"
125
125
  },
126
126
  "devDependencies": {
127
127
  "@eslint/js": "^10.0.1",
128
- "@lexical/code": "^0.52.0",
129
- "@lexical/code-prism": "^0.52.0",
130
- "@lexical/link": "^0.52.0",
131
- "@lexical/list": "^0.52.0",
132
- "@lexical/mark": "^0.52.0",
133
- "@lexical/markdown": "^0.52.0",
134
- "@lexical/react": "^0.52.0",
135
- "@lexical/rich-text": "^0.52.0",
136
- "@lexical/selection": "^0.52.0",
137
- "@lexical/table": "^0.52.0",
138
- "@lexical/utils": "^0.52.0",
128
+ "@lexical/code": "^0.53.0",
129
+ "@lexical/code-prism": "^0.53.0",
130
+ "@lexical/link": "^0.53.0",
131
+ "@lexical/list": "^0.53.0",
132
+ "@lexical/mark": "^0.53.0",
133
+ "@lexical/markdown": "^0.53.0",
134
+ "@lexical/react": "^0.53.0",
135
+ "@lexical/rich-text": "^0.53.0",
136
+ "@lexical/selection": "^0.53.0",
137
+ "@lexical/table": "^0.53.0",
138
+ "@lexical/utils": "^0.53.0",
139
139
  "@testing-library/react": "^16.3.3",
140
140
  "@types/mdast": "^4.0.4",
141
- "@types/node": "^24.19.1",
141
+ "@types/node": "^24.19.2",
142
142
  "@types/react": "^19.3.0",
143
143
  "@types/react-dom": "^19.3.0",
144
- "@vitejs/plugin-react": "^6.1.1",
145
- "@vitest/coverage-v8": "^4.1.5",
144
+ "@vitejs/plugin-react": "^6.3.0",
145
+ "@vitest/coverage-v8": "^5.1.0",
146
146
  "diff": "^9.0.0",
147
- "eslint": "^10.11.0",
147
+ "eslint": "^10.14.0",
148
148
  "eslint-plugin-react-hooks": "^7.1.1",
149
149
  "eslint-plugin-react-refresh": "^0.5.7",
150
- "globals": "^17.13.0",
151
- "happy-dom": "^20.14.5",
152
- "lexical": "^0.52.0",
153
- "react": "^19.3.0",
154
- "react-dom": "^19.3.0",
155
- "semver": "^7.8.5",
156
- "tsc-alias": "^1.9.7",
150
+ "globals": "^17.14.0",
151
+ "happy-dom": "^21.0.4",
152
+ "lexical": "^0.53.0",
153
+ "react": "^19.3.1",
154
+ "react-dom": "^19.3.1",
155
+ "semver": "^7.8.6",
156
+ "tsc-alias": "^1.9.10",
157
157
  "typescript": "^6.0.3",
158
- "typescript-eslint": "^8.71.0",
159
- "vitest": "^4.1.5"
158
+ "typescript-eslint": "^8.72.2",
159
+ "vitest": "^5.1.0"
160
160
  },
161
161
  "repository": {
162
162
  "type": "git",