$ bazel run //:refresh_compile_commands
INFO: Invocation ID: 36544ffc-7920-498f-a309-f8c4a2c13292
INFO: Build options --@rules_rust//:extra_rustc_flags, --cxxopt, --host_cxxopt, and 3 more have changed, discarding analysis cache.
INFO: Analyzed target //:refresh_compile_commands (1 packages loaded, 455 targets configured).
INFO: Found 1 target...
Target //:refresh_compile_commands up-to-date:
  bazel-bin/refresh_compile_commands.py
  bazel-bin/refresh_compile_commands
INFO: Elapsed time: 0.433s, Critical Path: 0.00s
INFO: 2 processes: 2 internal.
INFO: Build completed successfully, 2 total actions
INFO: Running command line: bazel-bin/refresh_compile_commands
>>> Analyzing commands used in @//...
>>> A source file you compile doesn't (yet) exist: bazel-out/k8-fastbuild/bin/src/cloudflare/cfbundle.capnp.c++
    It's probably a generated file, and you haven't yet run a build to generate it.
    That's OK; your code doesn't even have to compile for this tool to work.
    If you can, though, you might want to run a build of your code.
        That way everything is generated, browsable and indexed for autocomplete.
    However, if you have *already* built your code, and generated the missing file...
        Please make sure you're supplying this tool with the same flags you use to build.
        You can either use a refresh_compile_commands rule or the special -- syntax. Please see the README.
        [Supplying flags normally won't work. That just causes this tool to be built with those flags.]
    Continuing gracefully...
>>> While locating the headers you use, we encountered a compiler warning or error.
    No need to worry; your code doesn't have to compile for this tool to work.
    However, we'll still print the errors and warnings in case they're helpful for you in fixing them.
    If the errors are about missing files that Bazel should generate:
        You might want to run a build of your code with --keep_going.
        That way, everything possible is generated, browsable and indexed for autocomplete.
    But, if you have *already* built your code successfully:
        Please make sure you're supplying this tool with the same flags you use to build.
        You can either use a refresh_compile_commands rule or the special -- syntax. Please see the README.
        [Supplying flags normally won't work. That just causes this tool to be built with those flags.]
    Continuing gracefully...
In file included from bazel-out/k8-fastbuild/bin/src/workerd/jsg/modules.capnp.c++:4:
bazel-out/k8-fastbuild/bin/src/workerd/jsg/modules.capnp.h:10:2: error: "CAPNP_VERSION is not defined, is capnp/generated-header-support.h missing?"
#error "CAPNP_VERSION is not defined, is capnp/generated-header-support.h missing?"
 ^
1 error generated.
In file included from bazel-out/k8-fastbuild/bin/icudata-embed.capnp.c++:4:
bazel-out/k8-fastbuild/bin/icudata-embed.capnp.h:10:2: error: "CAPNP_VERSION is not defined, is capnp/generated-header-support.h missing?"
#error "CAPNP_VERSION is not defined, is capnp/generated-header-support.h missing?"
 ^

>>> Analyzing commands used in @//...
>>> A source file you compile doesn't (yet) exist: bazel-out/k8-opt-exec-2B5CBBC6/bin/src/workerd/server/workerd.capnp.c++
    It's probably a generated file, and you haven't yet run a build to generate it.
    That's OK; your code doesn't even have to compile for this tool to work.
    If you can, though, you might want to run a build of your code.
        That way everything is generated, browsable and indexed for autocomplete.
    However, if you have *already* built your code, and generated the missing file...
        Please make sure you're supplying this tool with the same flags you use to build.
        You can either use a refresh_compile_commands rule or the special -- syntax. Please see the README.
        [Supplying flags normally won't work. That just causes this tool to be built with those flags.]
    Continuing gracefully...
>>> Finished extracting commands for @//...