build: update dependency aspect_rules_js to v2.7.0 (main)

[angular-robot]

This PR contains the following updates:

Package	Type	Update	Change
aspect_rules_js	bazel_dep	minor	2.6.2 -> 2.7.0

---

Release Notes

aspect-build/rules_js (aspect_rules_js)

v2.7.0

Many companies are successfully building with rules_js.
If you're getting value from the project, please let us know!
Just comment on our Adoption Discussion.

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_js", version = "2.7.0")

####### Node.js version #########

### By default you get the node version from DEFAULT_NODE_VERSION in @​rules_nodejs//nodejs:repositories.bzl
### Optionally you can pin a different node version:
bazel_dep(name = "rules_nodejs", version = "6.3.0")
node = use_extension("@​rules_nodejs//nodejs:extensions.bzl", "node", dev_dependency = True)
node.toolchain(node_version = "18.14.2")

#################################

npm = use_extension("@​aspect_rules_js//npm:extensions.bzl", "npm", dev_dependency = True)

npm.npm_translate_lock(
    name = "npm",
    pnpm_lock = "//:pnpm-lock.yaml",
    verify_node_modules_ignored = "//:.bazelignore",
)

use_repo(npm, "npm")

pnpm = use_extension("@​aspect_rules_js//npm:extensions.bzl", "pnpm")

### Allows developers to use the matching pnpm version, for example:
### bazel run -- @​pnpm --dir /home/runner/work/rules_js/rules_js install
use_repo(pnpm, "pnpm")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "aspect_rules_js",
    sha256 = "9dd50d3bacb2fe1d4a721098981b70290fe9ac56d3625791f490d2ab94f2cac6",
    strip_prefix = "rules_js-2.7.0",
    url = "https://github.com/aspect-build/rules_js/releases/download/v2.7.0/rules_js-v2.7.0.tar.gz",
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​aspect_rules_js//js:toolchains.bzl", "DEFAULT_NODE_VERSION", "rules_js_register_toolchains")

rules_js_register_toolchains(node_version = DEFAULT_NODE_VERSION)

load("@​aspect_rules_js//npm:repositories.bzl", "npm_translate_lock")

npm_translate_lock(
    name = "npm",
    npmrc = "//:.npmrc",
    pnpm_lock = "//:pnpm-lock.yaml",
    verify_node_modules_ignored = "//:.bazelignore",
)

load("@​npm//:repositories.bzl", "npm_repositories")

npm_repositories()

What's Changed

• test: use rules_shell for sh_* in tests by @​jbedard in #​2390
• chore: remove BCR homepage, as we now use the BCR UI itself by @​alexeagle in #​2391
• Fix js_run_devserver shell script tools on Windows by @​AlexHickie in #​2393
• Changes by create-pull-request action by @​github-actions[bot] in #​2392
• feat: support prod and dev deps on npm_link_all_packages and npm_link_targets by @​Mivr in #​2298
• Remove usage of dicts.add by @​dzbarsky in #​2396
• Stop reading pnpm_lock from label_store, take 2 by @​dzbarsky in #​2395
• Remove host_yq from label_store by @​dzbarsky in #​2398
• Changes by create-pull-request action by @​github-actions[bot] in #​2394
• feat: add dev script to update snapshots by @​Mivr in #​2397

New Contributors

• @​AlexHickie made their first contribution in #​2393

Full Changelog: aspect-build/rules_js@v2.6.2...v2.7.0

---

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 5:00am every weekday,every weekend" in timezone America/Tijuana, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[ngbot]

I see that you just added the action: merge label, but the following checks are still failing:
     conflicts with base branch "main"
     status "mergeability" is failing
If you want your PR to be merged, it has to pass all the CI checks.
If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[ngbot]

I see that you just added the action: merge label, but the following checks are still failing:
     conflicts with base branch "main"
     status "mergeability" is failing
If you want your PR to be merged, it has to pass all the CI checks.
If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}