Contributing
Thanks for improving @manovaspace/* — MIT TypeScript libraries on npm and GitHub.
Which repo?
Section titled “Which repo?”| Change | Repo |
|---|---|
| tsconfig, markdown, pwa, observability | manovaspace/ts |
| tokens, ui, devtools | manovaspace/design-system |
| This documentation site | manovaspace/docs |
Before you open a PR
Section titled “Before you open a PR”- Scope — Keep packages generic and reusable. No client product names, private URLs, or new
Orbit-prefixed package names on npm. - Changeset — User-facing package changes need a changeset in that package repo.
- Docs — API changes that affect consumers should update this site (or link a docs PR).
Development (package repos)
Section titled “Development (package repos)”pnpm installpnpm buildpnpm testpnpm typecheckpnpm lintChangesets
Section titled “Changesets”pnpm changesetPick affected packages and the semver bump. Commit .changeset/*.md with your PR.
Releases: ts RELEASING.md · design-system RELEASING.md
Documentation site
Section titled “Documentation site”This repo uses npm (single Starlight app, no pnpm workspace).
cd manovaspace/docs # or: git clone https://github.com/manovaspace/docs.gitnpm installnpm run devnpm run buildLegacy identifiers
Section titled “Legacy identifiers”Some TypeScript exports still use Orbit* names (for example OrbitDevtoolsProvider, OrbitTokensRaw). The product and npm packages are @manovaspace/*. Prefer documenting the real export name; a rename is tracked separately and is not required for contributions.
Questions
Section titled “Questions”Open a GitHub issue or an issue on the package repo.