Update dependency @angular-devkit/build-angular to ^12.2.18

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@angular-devkit/build-angular	^12.2.14 -> ^12.2.18

---

Release Notes

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

v12.2.18

Compare Source

12.2.18 (2022-07-21)

@​angular-devkit/build-angular

Commit	Description
	update terser to address CVE-2022-25858

Special Thanks

Alan Agius, Joey Perrott and Paul Gschwendtner

v12.2.17

Compare Source

@​angular-devkit/architect-cli

Commit	Type	Description
ccb0f95f3	fix	update minimist to 1.2.6

@​angular-devkit/schematics-cli

Commit	Type	Description
abcdf4df2	fix	update minimist to 1.2.6

@​angular-devkit/benchmark

Commit	Type	Description
2656a330e	fix	update minimist to 1.2.6

Special Thanks

Alan Agius

v12.2.16

Compare Source

12.2.16 (2022-01-31)

@​angular-devkit/build-angular

Commit	Type	Description
ebfdcc635	fix	invalid browsers version ranges

Special Thanks

Alan Agius

v12.2.15

Compare Source

@​angular-devkit/build-angular

Commit	Type	Description
526115fdb	fix	updated webpack-dev-server to latest security patch

Special Thanks

Doug Parker and iRealNirmal

---

Configuration

📅 Schedule: Branch creation - "after 2am and before 7am every weekday,after 2am and before 7am every weekend" in timezone Asia/Yangon, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact 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-lock.json

npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/compiler-cli
npm ERR!   dev @angular/compiler-cli@"^11.2.14" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler-cli@"^12.0.0" from @angular-devkit/[email protected]
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev @angular-devkit/build-angular@"^12.2.18" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/a6d47b/ee4da8/cache/others/npm/_logs/2023-07-07T20_37_50_079Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/a6d47b/ee4da8/cache/others/npm/_logs/2023-07-07T20_37_50_079Z-debug-0.log

[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.}