[Bug]: eslint error does not always get reported to stdout on first run

[jgao54]

What happened?

When running bazel lint, the eslint error does not consistently get printed to stdout on initial build (seems like a race condition of some sort). It always gets captured in the .report file. Subsequent cached builds via bazel lint get printed to stdout.

Version

Development (host) and target OS/architectures:

Output of bazel --version: 7.1.1

Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:

http_archive(
    name = "aspect_rules_lint",
    sha256 = "a3e07f07216b6b406d2297c273e7af4cc8096b43288952020cdf4dc12f45b5e8",
    strip_prefix = "rules_lint-0.18.0",
    url = "https://github.com/aspect-build/rules_lint/releases/download/v0.18.0/rules_lint-v0.18.0.tar.gz",
)

How to reproduce

No response

Any other information?

No response