Contributing
How to work in the Spry monorepo, run the docs app, and propose changes with Changesets.
Repository
SpryInnovation uses pnpm workspaces and Turbo for orchestration. Packages live under packages/* and apps under apps/*.
Local development
Install dependencies from the repository root, then run builds or target a single app (for example the docs site on its configured port).
Commands
Changesets & releases
User-facing package changes should include a Changeset so versions and changelogs stay aligned:
pnpm changeset— describe the impact (patch/minor/major) per package.pnpm version-packages— apply version bumps (maintainers).pnpm release— publish when wired to a registry (maintainers).
Quality bar
Before merging: pnpm lint and pnpm test where applicable; for UI changes, verify light/dark and keyboard focus. New primitives should document props and accessibility notes in the docs app.