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

[peterjokumsen]

This PR contains the following updates:

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

---

Release Notes

nrwl/nx (@​nx/angular)

v19.0.5

Compare Source

19.0.5 (2024-05-21)

🚀 Features

• bundling: added support for declarations (*.d.ts) (#​21084)
• core: resolve nx migrate target version against registry (#​23450)
• core: allow executor definition to point to another executor (#​23576)
• graph: change gradle and nextjs svg (#​23201)

🩹 Fixes

• angular: libraries should not contain tslib by default #​21023 (#​23423, #​21023)
• angular: @​angular/core should always be provided as a shared package #​19121 (#​23464, #​19121)
• core: do not add an ending new line when serializing a json (#​23440)
• core: migrate should warn if package does not exist (#​23317)
• core: azure ci workflow (#​23453)
• core: only check for err in handleWorkspaceChanges (#​23500)
• core: remove duplicate js-yaml packages (2eaf79b65)
• core: fix alias package parsing and pruning for npm (#​23474)
• core: install packages per migration when creating commits (#​23820)
• devkit: combineAsyncIterable should not be blocking when error occurs #​21393 (#​23400, #​21393)
• graph: reload graph app only when hash changes in watch mode (#​23434)
• js: Respect loose option provided from config (#​23406)
• js: fix update package.json (#​21415)
• nextjs: additional experimental HTTPS options (#​23334)
• node: Docker generator should work (#​23452)
• react: respect unitTestRunner passed to the generator (#​23383)
• react: remote generator should update host's app routes (#​23499)
• react: applications not using plugin usage should set target defaults (#​23582)
• react-native: fix test-setup for react native/expo jest (#​23314)
• release: invalid tag for fixed groups without changes (#​22800)
• repo: hash proper projects when nx (#​23506)
• testing: handle existing jest preset file correctly (#​23437)
• vite: add prop to config to ensure output dir is emptied #​23382 (#​23466, #​23382)
• vue: ootb unit testing should work with --routing #​19921 (#​23441, #​19921)
• web: Add strict mode (#​23457)
• web: Add strict mode" (#​23472)
• web: Add strict mode for @​nx/web (#​23497)
• webpack: only add entrypoints if they are intentionally injected #​20049 (#​23444, #​20049)

❤️ Thank You

• castleadmin @​castleadmin
• Colum Ferry @​Coly010
• Craigory Coppola @​AgentEnder
• Emily Xiong @​xiongemi
• Isaac Mann @​isaacplmann
• Jack Hsu @​jaysoo
• James Henry @​JamesHenry
• Jason Jean @​FrozenPandaz
• Jonathan Cammisuli
• Katerina Skroumpelou @​mandarini
• Leosvel Pérez Espinosa @​leosvelperez
• MaxKless @​MaxKless
• Miroslav Jonaš @​meeroslav
• Nicholas Cunningham @​ndcunningham
• Phillip Barta @​Phillip9587
• Younes Jaaidi

---

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

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