This repository contains:
- the demo Next.js app in the workspace root
- the publishable npm package in packages/openmotion
npm install
npm run devBuild just the package:
npm run build --workspace openmotionPack the package tarball:
npm run pack:packagePublish the public npm package:
npm publish --workspace openmotion --access publicFor local terminal publishing, keep provenance off:
set NPM_CONFIG_PROVENANCE=false && npm publish --workspace openmotion --access publicThe root package is intentionally private, so publishing from the repository root with plain npm publish will fail with EPRIVATE.
The workflow in .github/workflows/publish-openmotion.yml is set up for GitHub Actions + npm trusted publishing + provenance.
After the first manual publish, configure the trust relationship:
npm trust github openmotion --repo YOUR_GITHUB_USER/YOUR_REPO --file .github/workflows/publish-openmotion.yml --allow-publishThen release from GitHub instead of using long-lived npm tokens.
Note: npm’s trusted publishing docs say automatic provenance generation works when publishing from supported CI/CD providers. A local terminal publish does not have a provider, so forcing provenance locally causes the provider: null error.
Official npm docs: