feat: add more utility tools (#350)

* feat: add more utility tools

pnpm is especially useful for frontend engineers

Also run 'multitool update' to get newer versions

* refactor: simplify

* chore: update bazel readme

* Update README.bazel.md

Author: alexeagle

README.bazel.md

@@ -39,20 +39,34 @@ For a more robust developer experience, see the [sample shell script](https://gi
 For developers to be able to run a CLI tool without needing manual installation:
 
 1. Add the tool to `tools/tools.lock.json`
-2. `cd tools; ln -s _multitool_run_under_cwd.sh name_of_tool`
+2. `cd tools; ln -s _run_under_cwd.sh name_of_tool`
 3. Instruct developers to run `./tools/name_of_tool` rather than install that tool on their machine.
 
+To update the versions of installed tools, run:
+
+```shell
+% cd $(bazel info workspace)/tools; ./multitool --lockfile tools.lock.json update
+```
+
 See https://blog.aspect.build/run-tools-installed-by-bazel for details.
 
 ## Working with npm packages
 
-To install a `node_modules` tree locally for the editor or other tooling outside of Bazel:
+To install a `node_modules` tree locally for the editor or other tooling outside of Bazel,
+run this command from any folder with a `package.json` file:
 
+```shell
+% $(bazel info workspace)/tools/pnpm install
 ```
-bazel run -- @pnpm --dir $PWD install
+
+> NB: `bazel info workspace` avoids having a bunch of `../` segments when running tools from a subdirectory.
+
+Similarly, you can run other `pnpm` commands to add or remove packages.
+
+```shell
+% $(bazel info workspace)/tools/pnpm add http-server
 ```
 
-Similarly, you can run other `pnpm` commands to install or remove packages.
 This ensures you use the same pnpm version as other developers, and the lockfile format will stay constant.
 
 ## Working with Python packages
@@ -88,11 +102,12 @@ Then edit the new entry in `tools/BUILD` to replace `package_name_snake_case` wi
 
 After adding a new `import` statement in Go code, run `bazel configure` to update the BUILD file.
 
-If the package is not already a dependency of the project, you'll have to do some additional steps:
+If the package is not already a dependency of the project, you'll have to do some additional steps.
+Run these commands from the workspace root:
 
 ```shell
 # Update go.mod and go.sum, using same Go SDK as Bazel
-% bazel run @rules_go//go -- mod tidy -v
+% $(bazel info workspace)/tools/go mod tidy -v
 # Update MODULE.bazel to include the package in `use_repo`
 % bazel mod tidy
 # Repeat

tools/_multitool_run_under_cwd.sh

@@ -0,0 +1,17 @@
+#!/bin/sh
+# See https://blog.aspect.build/run-tools-installed-by-bazel
+case "$(basename "$0")" in
+  go)
+    # https://github.com/bazelbuild/rules_go/blob/master/docs/go/core/bzlmod.md#using-a-go-sdk
+    target="@rules_go//go"
+    ;;
+  pnpm)
+    # https://github.com/aspect-build/rules_js/blob/main/docs/faq.md#can-i-use-bazel-managed-pnpm
+    target="@pnpm"
+    ;;
+  *)
+    target="@multitool//tools/$(basename "$0")"
+    ;;
+esac
+# NB: we don't use 'bazel run' because it may leave behind zombie processes under ibazel
+bazel 2>/dev/null build "$target" && BAZEL_BINDIR=. exec $(bazel info execution_root)/$(bazel 2>/dev/null cquery --output=files "$target") "$@"

tools/_run_under_cwd.sh

@@ -0,0 +1 @@
+./_run_under_cwd.sh

tools/buf

@@ -1 +1 @@
-./_multitool_run_under_cwd.sh
+./_run_under_cwd.sh

tools/buildozer

@@ -0,0 +1 @@
+./_run_under_cwd.sh

tools/docker-compose

@@ -0,0 +1 @@
+./_run_under_cwd.sh

tools/go

@@ -1 +1 @@
-./_multitool_run_under_cwd.sh
+./_run_under_cwd.sh

tools/ibazel

@@ -0,0 +1 @@
+./_run_under_cwd.sh

tools/multitool

@@ -0,0 +1 @@
+./_run_under_cwd.sh