[deps]: Update eslint-plugin-rxjs-angular-x to v1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-rxjs-angular-x	0.1.0 → 1.0.0

---

Release Notes

JasonWeinzierl/eslint-plugin-rxjs-angular-x (eslint-plugin-rxjs-angular-x)

v1.0.0

Compare Source

Breaking Changes

• ESLint v10 is required (#​30) (2698833)
• Node.js ^20.19.0 || ^22.13.0 || >=24 is required; Node.js v18 is no longer supported
• ESM is required; CommonJS is no longer supported

Chores

• @typescript-eslint/utils ^8.56.0 is required
• ts-api-utils ^2.4.0 is required
• common-tags is no longer required
• docs folder is no longer published to npm

Summarized Changes from eslint-plugin-rxjs-angular

Since this is the first non-v0 release, the following re-states relevant pre-release changes after forking eslint-plugin-rxjs-angular:

Breaking Changes

• The namespace for this forked plugin is rxjs-angular-x
• TypeScript >=4.8.4 <6.0.0 is required
• tslib ^2.1.0 is required

Features

• prefer-composition and prefer-takeuntil: add superClass option. (#​3) (6dd8003)
• Support plugin.meta.namespace (#​20) (510d75d)

Chores

• The following dependencies are no longer required:
  • eslint-etc
  • requireindex
  • tsutils
  • tsutils-etc
• Add requiresTypeChecking to meta.docs of relevant rules
• The URL for each rule now aligns with the installed version of this plugin, instead of latest main. (11c7a09)
• Add names to rule tests (#​29) (ef2dbaa)

---

v0.1.2

Compare Source

Chores

• Upper bound on peer dependencies (42b2e85)
  • rxjs ^7.2.0 (previously was >=7.2.0)
  • typescript >=4.8.4 <6.0.0 (previously was >=4.8.4)
• Add names to rule tests (#​29) (ef2dbaa)
• Add OpenSSF Scorecard (f4887ab)

v0.1.1

Compare Source

Features

• Support plugin.meta.namespace (#​20) (510d75d)

---

Configuration

📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @bitwarden/directory-connector@2026.2.0
npm error Found: eslint@9.39.1
npm error node_modules/eslint
npm error   dev eslint@"9.39.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^10.0.0" from eslint-plugin-rxjs-angular-x@1.0.0
npm error node_modules/eslint-plugin-rxjs-angular-x
npm error   dev eslint-plugin-rxjs-angular-x@"1.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-02T02_42_53_930Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-02T02_42_53_930Z-debug-0.log

[bitwarden-bot]

Internal tracking:

• ID: PM-32950
• Link: https://bitwarden.atlassian.net/browse/PM-32950

[sven-bitwarden]

Blocked by a long list of deps. See: #1023 (comment)

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 1.x releases. But if you manually upgrade to 1.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.