Consume the editor from npm, not from packages/ - #183
Merged
Conversation
The editor now lives in getlatentic/live-markdown and publishes itself, so Compose depends on `@latentic/live-markdown@^0.1.1` like any other consumer. 20,462 lines leave this repository; the history came with them via `git subtree split`, all 115 commits. Consuming it the way everyone else does is the point. The workspace arrangement resolved the package to its TypeScript SOURCE through a Vite alias and a matching tsconfig path, so Compose never once exercised the thing npm ships — which is how a broken declaration build sat unnoticed while every check here was green, and how the package's own README came to promise that mathematics needs no CSS import. `pnpm-workspace.yaml` stays, with no members, because deleting it was worse than keeping it: pnpm then searches UPWARD for a workspace to join, and silently captured a git worktree nested under the primary checkout — resolving the dependency back to that checkout's `packages/rich-editor` and reporting success. The file now exists to stop the search. Supersedes #182. Those two commits touched nothing outside the package and are already released in 0.1.0, so the fixes arrive here through the registry instead: * a `[…]` keeps its brackets until it resolves to a link * a table cell renders what the paragraph above it renders Verified against the published tarball rather than a link: typecheck clean, 548 tests passing, `pnpm build` succeeds, and the shipped bundle really does contain the bracket fix. The editor-package build step leaves CI with it. That gate has moved to the editor's own three-platform CI, where it belongs — and where, given a second platform for the first time, it immediately found two bugs the macOS-only browser tier had been hiding.
This was referenced Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The editor now lives in getlatentic/live-markdown and publishes itself. Compose depends on
@latentic/live-markdown@^0.1.1like any other consumer, and 20,462 lines leave this repository — history intact, all 115 commits carried across bygit subtree split.Why consuming it normally matters
The workspace arrangement resolved the package to its TypeScript source through a Vite alias and a matching tsconfig path. So Compose never once exercised the thing npm actually ships. That is how a broken declaration build sat unnoticed while every check here was green, and how the package's README came to promise that mathematics needs no CSS import — true of the source, false of the tarball.
Now the app builds against
dist/, resolved through the package's ownexports.pnpm-workspace.yamlstays, with no membersDeleting it was worse than keeping it. pnpm then searches upward for a workspace to join, found the primary checkout's, and silently captured a git worktree nested under it — resolving the dependency back to
packages/rich-editorin that checkout and reporting a successful install. The file now exists to stop the search, and says so.Supersedes #182
Those two commits touched nothing outside the package, and are already released in
0.1.0. The fixes therefore arrive here through the registry instead:[…]keeps its brackets until it resolves to a linkVerified against the published tarball
Not against a symlink:
pnpm typecheckpnpm testpnpm buildCI loses the editor-package build step
That gate has moved to the editor's own three-platform CI, where it belongs. Worth noting what happened the moment it ran anywhere but a Mac: it immediately found two bugs the macOS-only browser tier had been hiding — undo tests pressing Cmd literally where CodeMirror binds Ctrl, and a
treeAtparse budget with seven milliseconds of headroom that let a delete cross a fence boundary. Neither was platform-specific. A single-platform test tier is a single-platform claim.Release path
0.1.0and0.1.1both published through tag-triggered CI using trusted publishing — no npm token exists anywhere, and provenance is attested automatically.