Please get in touch before spending any significant time preparing contributions.
- Node.js and NPM, versions as per the root
package.json
engines
field - Lerna 4, just install it globally and it'll use this project's local version when run
Different versions may work, but majorly newer/older tooling versions are likely to cause upheaval in package-lock.json
files.
- Self-explanatory NPM scripts in root and packages
- Prettier and ESLint for code hygiene
- Verify there are no uncommitted changes
npm run ci
in rootnpm run lint
in the example project, check number of errors and presence of new expected ones../check-es-compat/bin/cli.js .
in the example project, it should produce the same errorslerna clean
thenlerna bootstrap
, verify no changes were introduced (e.g. topackage-lock.json
)
lerna version
, with arguments as appropriate for signifigance of release- Verify the commit that it made did what you expected
lerna publish from-git
- In GitHub's Releases tab, open the new tag then create a release out of it