Repository navigation
chore: scaffold the package, CI, release workflow, and component gallery - #1
Merged
Merged
Conversation
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.
Requested by mau
Before: relay-ui was an empty repository, and relay-cards and relay-chat each kept their own copies of tables, Markdown, and theme colors.
After: relay-ui is an
@relay-cli/uipackage with the same setup as relay-shell (TypeScript, React 19, Ink 7, tsup, Vitest, ESLint, Prettier, MIT), CI on Ubuntu and Windows with Node 22, 24 and 26, a manual release workflow that packs the tarball, and arelay-uicommand that shows a gallery of the components. The gallery is empty in this PR; each component PR adds a section.How: the configuration files are copied from relay-shell. Ink and React are peer dependencies so a tool renders the components with its own single copy of React.
enginesisnode >=22like relay-shell, because Ink 7 and Vitest 5 need Node 22.First of a stack: merge this, then the theme, spinner, table and Markdown PRs in order.