chore(deps): ⬆️ update nx monorepo

[peterjokumsen]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@angular-devkit/build-angular	18.0.1 -> 18.0.2
@angular-devkit/core	18.0.1 -> 18.0.2
@angular-devkit/schematics	18.0.1 -> 18.0.2
@angular/cli	18.0.1 -> 18.0.2
@nx/angular (source)	19.1.0 -> 19.1.1
@nx/eslint (source)	19.1.0 -> 19.1.1
@nx/eslint-plugin (source)	19.1.0 -> 19.1.1
@nx/jest (source)	19.1.0 -> 19.1.1
@nx/js (source)	19.1.0 -> 19.1.1
@nx/workspace (source)	19.1.0 -> 19.1.1
nx (source)	19.1.0 -> 19.1.1

---

Release Notes

angular/angular-cli (@​angular-devkit/build-angular)

v18.0.2

Compare Source

@​schematics/angular

Commit	Type	Description
9967c04b8	fix	check both application builder packages in SSR schematic
92b48ab14	fix	set builders assets option correctly for new applications

@​angular/build

Commit	Type	Description
3bb06c37d	fix	disable Worker wait loop for Sass compilations in web containers
c4cf35923	fix	print Sass @warn location
352879804	fix	support valid self-closing MathML tags in HTML index file
476f3084a	fix	support valid self-closing SVG tags in HTML index file

@​angular/pwa

Commit	Type	Description
acbffd236	fix	set manifest icons location to match assets builder option

nrwl/nx (@​nx/angular)

v19.1.1

Compare Source

19.1.1 (2024-05-29)

🚀 Features

• core: clean up show project --json false (#​23486)
• graph: add target group for scripts (#​26035)
• nx-dev: Add canary index (#​25982)
• nx-dev: improve the enteprise page (8881da766)
• webpack: Support incremental builds via buildLibsFromSource (#​25060)

🩹 Fixes

• bundling: rollup watch mode yields result from async iterable (#​26160)
• bundling: use watch mode for rollup plugin (#​26139)
• core: include dependencies when hashing nx executors (#​26024)
• core: do not re-read from nx.json for dependsOn (#​26033)
• core: add missing bun PM support (#​26084)
• core: prevent max buffer issues with bunlock files (#​25985)
• core: keep version for third party preset (#​23284)
• core: limit the amount of choices shown so that the prompt fits … (#​26132)
• core: fix preset empty (#​26142)
• graph: show script in header (#​26034)
• js: show lifecycle script contents in publish executor, scrub version in dry-run (#​23850)
• js: fix swc version warning (#​24034)
• nx-dev: Remove ToC from CI releases page (#​26040)
• nx-dev: case study link should open in new tab (becafca1a)
• react: full support custom secure host for module federation (#​25288)
• release: improve error handling for npm publish (#​26159)

❤️ Thank You

• Emily Xiong @​xiongemi
• Ivens Diego Müller @​vensller
• Jack Hsu @​jaysoo
• James Henry @​JamesHenry
• Jason Jean @​FrozenPandaz
• Jordan Hall @​Jordan-Hall
• Miroslav Jonas @​meeroslav
• Nicholas Cunningham @​ndcunningham
• Vadim Goy

---

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.

👻 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.

[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

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