- Clone the repo
- From the root, run
yarn && yarn start - Visit http://localhost:3000
Run yarn build && yarn test from the root of the repo.
To test individual modules, cd into them and run yarn test. For example, running the unit tests would be cd modules/react-arborist && yarn test.
Releases are driven by bin/release.mjs, invoked via yarn release. The script bumps the version, runs tests, and pushes a v* tag. The tag push triggers .github/workflows/publish.yml, which publishes to npm via Trusted Publishing (OIDC) — no token needed.
- On
main, with a clean working tree, updateCHANGELOG.mdwith a new# Version X.Y.Zsection for the upcoming version. Commit and push. - Run
yarn release <patch|minor|major|X.Y.Z>from the repo root. The script will:- Verify you're on
main, the working tree is clean, and you're in sync with the remote - Run unit tests and build
- Read the matching
# Version X.Y.Zsection fromCHANGELOG.md(fails if missing) - Bump
modules/react-arborist/package.json, commit it, and tagvX.Y.Z - Push the commit and tag to your tracking remote
- Create a GitHub Release for the tag using the changelog section as the body
- Verify you're on
- Watch
gh run watch— the publish workflow will build andnpm publishvia OIDC. Confirm the new version on https://www.npmjs.com/package/react-arborist.
Flags:
--preview— dry-run; the script still reads git state and builds, but no commit, tag, push, or release is created.--any-branch— skip both themainbranch check and the remote sync check (useful for testing on a branch that isn't pushed).--no-tests— skip the unit test step (yarn workspace react-arborist test).--yes— skip the interactive confirmation.
I run yarn build, then I copy the showcase/out directory into the netlify manual deploys interface.