Starlark files should be formatted by buildifier. We suggest using a pre-commit hook to automate this. First install pre-commit, then run
pre-commit install
Otherwise later tooling on CI may yell at you about formatting/linting violations.
Some targets are generated from sources.
Currently this is just the bzl_library
targets.
Run bazel run //:gazelle
to keep them up-to-date.
You'll commonly find that you develop in another WORKSPACE, such as
some other ruleset that depends on @aspect_rules_js
, or in a nested
WORKSPACE in the integration_tests folder.
To always tell Bazel to use this directory rather than some release artifact or a version fetched from the internet, run this from this directory:
OVERRIDE="--override_repository=aspect_rules_js=$(pwd)/rules_js"
echo "build $OVERRIDE" >> ~/.bazelrc
echo "query $OVERRIDE" >> ~/.bazelrc
This means that any usage of @aspect_rules_js
on your system will point to this folder.
- Push a tag to the repo, or create one on the GH UI
- Watch the automation run on GitHub actions