github.com/lestrrat-go/jwx/v2@v2.0.21/.aspect/bazelrc/javascript.bazelrc (about)

     1  # Aspect recommended Bazel flags when using Aspect's JavaScript rules: https://github.com/aspect-build/rules_js
     2  # Docs for Node.js flags: https://nodejs.org/en/docs/guides/debugging-getting-started/#command-line-options
     3  
     4  # Support for debugging Node.js tests. Use bazel run with `--config=debug` to turn on the NodeJS
     5  # inspector agent. The node process will break before user code starts and wait for the debugger to
     6  # connect. Pass the --inspect-brk option to all tests which enables the node inspector agent. See
     7  # https://nodejs.org/de/docs/guides/debugging-getting-started/#command-line-options for more
     8  # details.
     9  # Docs: https://nodejs.org/en/docs/guides/debugging-getting-started/#command-line-options
    10  run:debug -- --node_options=--inspect-brk
    11  
    12  # Enable runfiles on all platforms. Runfiles are on by default on Linux and MacOS but off on
    13  # Windows.
    14  #
    15  # In general, rules_js and derivate rule sets assume that runfiles are enabled and do not support no
    16  # runfiles case because it does not scale to teach all Node.js tools to use the runfiles manifest.
    17  #
    18  # If you are developing on Windows, you must either run bazel with administrator privileges or
    19  # enable developer mode. If you do not you may hit this error on Windows:
    20  #
    21  #   Bazel needs to create symlinks to build the runfiles tree.
    22  #   Creating symlinks on Windows requires one of the following:
    23  #       1. Bazel is run with administrator privileges.
    24  #       2. The system version is Windows 10 Creators Update (1703) or later
    25  #          and developer mode is enabled.
    26  #
    27  # Docs: https://bazel.build/reference/command-line-reference#flag--enable_runfiles
    28  build --enable_runfiles