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

[peterjokumsen]

This PR contains the following updates:

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

---

Release Notes

nrwl/nx (@​nx/angular)

v19.2.1

Compare Source

19.2.1 (2024-06-06)

🚀 Features

• graph: add source info for command and script (#​26162)
• node: Add output path to setup docker (#​26365)
• nx-dev: update text on enterprise & contact screens (#​26416)
• web: allow additional http-server options to be passed from @​nx/web:file-server (#​26391)

🩹 Fixes

• angular: install @​typescript-eslint/utils when using relevant angular eslint v18 packages (#​26418)
• bundling: load rollup config using the rollup version installed in the workspace (#​26298)
• core: make plugin pool cleanup to be synchronous (#​26389)
• core: handle paths deleted by the ide (#​26363)
• core: add quotes around string to command (#​23056)
• core: don't load env vars when insantiating daemon client (#​26421)
• core: should not pass --no-color --no-parallel (#​22763)
• core: fix postinstall when nx is not resolveable (#​26433)
• graph: make cacheable and nx release pill sticky to the right (#​26157)
• js: add default baseUrl when extracting tsconfig.base.json or building libs will fail (#​26432)
• linter: do not glob for invalid eslint config filenames in plugin (#​26409)
• linter: improve error message for misconfigured parserOptions.project in @​nx/eslint:lint executor (#​26383)
• misc: gitignore workspace-data when init run (#​26429)
• nextjs: enable failing storybook tests (#​22675)
• nuxt: generate tsconfig files correctly (#​26385)
• nuxt: app generation should respect as-provided for app names (#​26412)
• nuxt: ensure .output directory is marked as an output (#​26414)
• nx-dev: update section layout in 'how-can-we-help' component (#​26394)

❤️ Thank You

• Benjamin Cabanes @​bcabanes
• Colum Ferry @​Coly010
• Craigory Coppola @​AgentEnder
• Emily Xiong @​xiongemi
• Jack Hsu @​jaysoo
• Jason Jean @​FrozenPandaz
• Leosvel Pérez Espinosa @​leosvelperez
• Nicholas Cunningham @​ndcunningham

---

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