build: update all non-major dependencies

[angular-robot]

This PR contains the following updates:

Package	Type	Update	Change
@inquirer/confirm (source)	dependencies	patch	5.1.8 -> 5.1.9
@inquirer/prompts (source)	dependencies	patch	7.4.0 -> 7.4.1
aspect_rules_js	http_archive	patch	v2.3.3 -> v2.3.4
ng-packagr	devDependencies	patch	20.0.0-next.4 -> 20.0.0-next.5
sass	dependencies	patch	1.86.2 -> 1.86.3

---

Release Notes

SBoudrias/Inquirer.js (@​inquirer/confirm)

v5.1.9

Compare Source

aspect-build/rules_js (aspect_rules_js)

v2.3.4

Compare Source

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.3.4")

####### 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 = "16.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 = "373e912bd986c38e54da82f15174984563866d14b60c5392e5b39e82b3bdf576",
    strip_prefix = "rules_js-2.3.4",
    url = "https://github.com/aspect-build/rules_js/releases/download/v2.3.4/rules_js-v2.3.4.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

• Watch pnpm-lock from the module extension by @​patrickmscott in https://github.com/aspect-build/rules_js/pull/2148
• fix: bzlmod invalid lockfile entry error by @​jbedard in https://github.com/aspect-build/rules_js/pull/2149

New Contributors

• @​patrickmscott made their first contribution in https://github.com/aspect-build/rules_js/pull/2148

Full Changelog: aspect-build/rules_js@v2.3.3...v2.3.4

ng-packagr/ng-packagr (ng-packagr)

v20.0.0-next.5

Compare Source

Bug Fixes

• disable emitting empty chunk warning (638c107)

sass/dart-sass (sass)

v1.86.3

Compare Source

• Fix a bug introduced in 1.86.1 where Sass fails to resolve paths starting with
  a .. segment.

---

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 4: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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Renovate Bot.

[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.}