This is a bazel monorepo containing most of my side-projects and websites etc. Using a monorepo in this way makes it much easier to ensure linting and deployment are consistent across many projects, and prevents a lot of version rot.
The repo is going through a bit of an identity crisis at the moment. I have just completed migration to rules_js, which uses PNPM -- and the PNPM binary is controlled by bazel itself.
I recommend having a local 'bazel' installation. However, if you just have NPM installed, you can:
npx @bazel/bazelisk test //...
This will recursively run all tests in parallel.
The project is configured to use a BuildBuddy cache for faster build times. If you have an account, you can run BUILDBUDDY_API_KEY=EDIT_AND_REPLACE ./.github/workflows/bootstrap_remote_cache.sh from
the project root, and it will drop an .auth.bazelrc in there.
Once that's done, edit the file and replace EDIT_AND_REPLACE with your BuildBuddy API key. I do not recommend changing "EDIT_AND_REPLACE" on the bash commandline, or you'll end up having your secret API key stored in your shell history.
- Continuous patching. Because Bazel allows this repo to be fully tested, Mend is able to automatically integrate patches for any and all dependencies of any project in this repo automatically.
- Linting. There are central rules that enforce basic linting standards.
- Continuous deployment. Every day, this repo runs a deploy script which detects any changes in any files and re-deploys or publishes any changed packages or services.
- Automatic versioning. The packages published on NPM use the venerable api-extractor to detect major or minor version changes to the API, and automatically increment version numbers as relevant.