Publishing to npm

Publishing to npm

Patro now uses a manual npm release flow. GitHub Actions no longer publishes packages.

Packages

Package	npm	Description
@thaparoyal/calendar-core	npm	Date conversion, themes, shared logic
@thaparoyal/calendar-react	npm	React components and hooks
@thaparoyal/calendar-vue	npm	Vue composables
@thaparoyal/calendar-svelte	npm	Svelte stores
@thaparoyal/calendar-angular	npm	Angular services
@thaparoyal/calendar-vanilla	npm	Vanilla JS and CDN build
@thaparoyal/calendar-cli	npm	CLI tooling

---

Manual Release Steps

1) Create a changeset

pnpm changeset

Commit the generated .changeset/*.md file with your code changes.

2) Bump versions and changelogs

pnpm version-packages

3) Build and test

pnpm build
pnpm test

4) Publish to npm

npm login
pnpm release

pnpm release runs build + changeset publish and publishes updated packages.

5) Push version commits and tags

git push --follow-tags

---

Notes

• Do not use plain pnpm publish from the monorepo root.
• Packages are linked in .changeset/config.json, so they version together.
• Keep repository visibility public if packages are public on npm.