Bump @angular-devkit/core from 20.3.9 to 21.1.4 in /eform-client

[dependabot]

Bumps @angular-devkit/core from 20.3.9 to 21.1.4.

Release notes

Sourced from @​angular-devkit/core's releases.

21.1.4

@​angular/build

Commit	Description
	correctly resolve absolute setup file paths in Vitest

21.1.3

@​schematics/angular

Commit	Description
	warn when production configuration is missing for service worker

@​angular-devkit/build-angular

Commit	Description
	address Node.js deprecation DEP0190

21.1.2

@​angular-devkit/schematics-cli

Commit	Description
	Add boolean type inference for 'true' and 'false' string values in argument parsing

@​angular-devkit/architect

Commit	Description
	Add boolean type inference for 'true' and 'false' string values in argument parsing

@​angular/build

Commit	Description
	loosen Vitest dependency checks when runnerConfig is used
	support merging coverage thresholds with Vitest runnerConfig

21.1.1

@​schematics/angular

Commit	Description
	correct vscode MCP configuration for new projects
	remove special characters from jasmine-vitest report filename

@​angular/cli

Commit	Description
	Remove nonexistent link from MCP response

@​angular/build

Commit	Description
	allow application assets in workspace root
	prevent incorrect catch binding removal in downleveled for-await
	update undici to v7.18.2

21.1.0

@​schematics/angular

... (truncated)

Changelog

Sourced from @​angular-devkit/core's changelog.

21.1.4 (2026-02-11)

@​angular/build

Commit	Type	Description
7a9dd6b47	fix	correctly resolve absolute setup file paths in Vitest

20.3.16 (2026-02-09)

@​angular/cli

Commit	Type	Description
656888a25	fix	update dependency @​modelcontextprotocol/sdk to v1.26.0

21.2.0-next.1 (2026-02-05)

@​angular/cli

Commit	Type	Description
91b9d281f	feat	integrate file formatting into update migrations
6f29a8c35	fix	renamed files by their new path in the schematic workflow
bc363af8b	perf	optimize package manager discovery with stat-based probing

@​schematics/angular

Commit	Type	Description
5d1df50d8	fix	add actionable feedback to vitest-browser schematic
51fc77828	fix	warn when production configuration is missing for service worker

@​angular/build

Commit	Type	Description
ece30f235	feat	add headless option to unit-test builder
1f114a9e8	fix	bundle setup files in unit-test builder for Vitest

... (truncated)

Commits

• aa6eef5 release: cut the v21.1.4 release
• 634cd54 build: lock file maintenance
• fe1fb42 build: update cross-repo angular dependencies
• 99edb0e build: update pnpm to v10.29.1
• 7a9dd6b fix(@​angular/build): correctly resolve absolute setup file paths in Vitest
• 0a8860d release: cut the v21.1.3 release
• e80d7c5 build: update dependency @​modelcontextprotocol/sdk to v1.26.0
• f6cc58c build: update webpack dependency to version 5.105.0
• 133cf28 build: update cross-repo angular dependencies to v21.1.3
• ed0b4c5 build: update rules_browsers digest to e08ae33
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}