Thanks for contributing to Seqvio.
- Use Node.js
>=18. - Use
pnpm >=8as the canonical package manager for this repo. - Read README.md for current scope and docs/COMPOSITION-AUTHORING.md for the active authoring contract.
pnpm install
pnpm buildUseful validation commands:
pnpm --filter @seqvio/renderer run render:smoke
pnpm --filter @seqvio/renderer run render:composition-smoke
pnpm --filter @seqvio/renderer run render:multiscene-smoke
pnpm --filter @seqvio/renderer run render:caption-smoke- Keep docs aligned with current code, not planning docs.
- Separate current behavior from proposals and roadmap notes.
- Prefer small, reviewable pull requests.
- Update examples or docs when changing public APIs or workflows.
- Do not commit secrets, generated local
.envfiles, or machine-specific output.
Include:
- a short description of the change
- why the change is needed
- validation performed
- screenshots or render outputs when the change affects visuals
- Treat code, examples, and
docs/COMPOSITION-AUTHORING.mdas implementation truth. - Keep positioning and scope in
docs/VISION.md; keep active work items in GitHub issues and milestones, not in docs. - Mark speculative or historical material clearly and keep it under
docs/archive/or other non-current locations. - Prefer fixing or removing stale docs over leaving conflicting guidance in place.
Publishable packages:
@seqvio/whiteboard@seqvio/core@seqvio/renderer
The root seqvio package is private and is not published.
Release flow:
pnpm install
pnpm build
pnpm changeset # record semver intent for changed packages
pnpm version # bump versions and changelogs
npm login # once per machine, or use NPM_TOKEN in CI
pnpm release # build + publish via changesetsBefore the first publish:
- Create the
@seqvionpm organization (or confirm scope ownership). - Ensure each package has
publishConfig.access: "public". - Validate tarballs locally:
pnpm --filter @seqvio/renderer pack- Smoke-test the packed CLI in a temp directory before
pnpm release.