Repository navigation
chore(packages): READMEs for the 6 published libs + stable dev userData name - #236
Merged
Merged
Conversation
…ta name
- README.md for @brainstorm-os/{block-protocol,sdk-types,tokens,react-yjs,sdk,
editor} — they published to npm without one (prepare-publish.mjs already
copies README.md into dist, so the next publish ships them).
- Pin the Electron app name to a STABLE value independent of the npm package
name: packaged = "Brainstorm", dev = "brainstorm-dev". Previously dev kept
the package name as its userData dir, so the @brainstorm→@brainstorm-os
rename silently moved dev's userData to a fresh empty dir and orphaned the
vault registry. "brainstorm-dev" stays distinct from "Brainstorm" so the
packaged app's single-instance lock still doesn't collide with a dev session.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
#1 publish-hygiene follow-ups.
@brainstorm-os/{block-protocol,sdk-types,tokens,react-yjs,sdk,editor}— they published without one.prepare-publish.mjsalready copiesREADME.mdintodist, so the next publish (a0.0.2) ships them.app.setName(isDev ? "brainstorm-dev" : "Brainstorm"). Dev previously keyed userData off the npm package name, so the scope rename moved it to a fresh empty dir and orphaned the vault registry (the vault-list-empty incident). Pinning it tobrainstorm-devkeeps dev distinct from the packaged app (single-instance lock) and immune to future renames.Note: the dev userData dir changes once with this (→
~/Library/Application Support/brainstorm-dev); the vault data in~/Documentsis untouched, and the registry pointer is migrated separately.🤖 Generated with Claude Code