chore(deps): ⬆️ update nx monorepo to v19.1.2

[peterjokumsen]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nx/angular (source)	19.1.1 -> 19.1.2
@nx/eslint (source)	19.1.1 -> 19.1.2
@nx/eslint-plugin (source)	19.1.1 -> 19.1.2
@nx/jest (source)	19.1.1 -> 19.1.2
@nx/js (source)	19.1.1 -> 19.1.2
@nx/workspace (source)	19.1.1 -> 19.1.2
nx (source)	19.1.1 -> 19.1.2

---

Release Notes

nrwl/nx (@​nx/angular)

v19.1.2

Compare Source

19.1.2 (2024-06-03)

🚀 Features

• nx-dev: add engineering team contact page (#​26293)
• react-native: upgrade react native to 0.74 (#​26143)
• vite: set watch:false in test config by default (#​26267)

🩹 Fixes

• angular: update angular-eslint to v18 (#​26165)
• angular: update broken imports in ng-packagr executors (#​26319)
• angular: normalize and handle dev remotes correctly (#​26320)
• core: handle relative paths after {projectRoot} in outputs (#​26244)
• core: prefer project specific external deps (#​23307)
• core: multi module handling and fall back matching for external nodes (#​26277)
• core: prevent graph output from being truncated (#​23446)
• core: fix daemon plugins caching (#​26321)
• expo: remove deprecated webpack. (#​26137)
• gradle: use os specific line separator for dependency parsing (#​26119)
• linter: support lib as standalone src path (#​26263)
• linter: handle configuration without "rules" in migration (#​26317)
• linter: return callback to install deps when running eslint migration to flat config generator (#​26323)
• misc: add externalDependencies input to some plugins missing them (#​26291)
• react: disable react refresh overlay (#​22013)
• react-native: not cache pod-install (#​26279)
• vite: ensure installed version matches defined peer in package.json (#​26324)

❤️ Thank You

• Benjamin Cabanes @​bcabanes
• Colum Ferry @​Coly010
• Craigory Coppola @​AgentEnder
• Emily Xiong @​xiongemi
• James Henry @​JamesHenry
• Jason Jean @​FrozenPandaz
• Leosvel Pérez Espinosa @​leosvelperez
• Miroslav Jonaš @​meeroslav
• Román Benjámin @​Svetch
• Zoran Kokeza @​zoran995

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

---

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

---

This PR has been generated by Renovate Bot.

[peterjokumsen]

⚠️ Artifact update problem

Renovate failed to update artifacts 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.json

Command failed: npm install --ignore-scripts
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @helderberg-pirates-baseball/[email protected]
npm error Found: @angular-eslint/[email protected]
npm error node_modules/@angular-eslint/eslint-plugin
npm error   dev @angular-eslint/eslint-plugin@"18.0.1" from the root project
npm error
npm error Could not resolve dependency:
npm error dev @angular-eslint/eslint-plugin@"18.0.1" from the root project
npm error
npm error Conflicting peer dependency: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/utils
npm error   peer @typescript-eslint/utils@"^7.11.0 || ^8.0.0-alpha.20" from @angular-eslint/[email protected]
npm error   node_modules/@angular-eslint/eslint-plugin
npm error     dev @angular-eslint/eslint-plugin@"18.0.1" 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 /home/ubuntu/.npm/_logs/2024-06-08T01_18_35_649Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-06-08T01_18_35_649Z-debug-0.log

File name: package.json

Command failed: npx --no-install nx run-many --target=lint --all --parallel --fix --skip-nx-cache

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -f package-lock.json' has not been added to the allowed list in allowedPostUpgradeCommands

File name: package.json

Post-upgrade command 'rm -rf node_modules' has not been added to the allowed list in allowedPostUpgradeCommands