build: update all non-major dependencies

[angular-robot]

This PR contains the following updates:

Package	Type	Update	Change
terser (source)	dependencies	patch	5.31.4 -> 5.31.5
terser (source)	devDependencies	patch	5.31.4 -> 5.31.5
undici (source)	devDependencies	patch	6.19.5 -> 6.19.7
vite (source)	dependencies	minor	5.3.5 -> 5.4.0
vite (source)	devDependencies	minor	5.3.5 -> 5.4.0

---

Release Notes

terser/terser (terser)

v5.31.5

Compare Source

• Revert v5.31.4, which created mysterious issues #​1548, #​1549

nodejs/undici (undici)

v6.19.7

Compare Source

Full Changelog: nodejs/undici@v6.19.6...v6.19.7

v6.19.6

Compare Source

Full Changelog: nodejs/undici@v6.19.5...v6.19.6

vitejs/vite (vite)

v5.4.0

• fix(build): windows platform build output path error (#​17818) (6ae0615), closes #​17818
• fix(deps): update launch-editor to consume fix for windows paths (#​17828) (cf2f90d), closes #​17828
• fix(ssr): fix global variable name conflict (#​17809) (6aa2206), closes #​17809
• fix(worker): fix importScripts injection breaking iife code (#​17827) (bb4ba9f), closes #​17827
• chore: bump typescript-eslint to v8 (#​17624) (d1891fd), closes #​17624
• chore(deps): update all non-major dependencies (#​17820) (bb2f8bb), closes #​17820
• perf(ssr): do a single-pass over AST with node cache arrays (#​17812) (81327eb), closes #​17812

---

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 4:00am every weekday,every weekend" in timezone America/Tijuana, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[clydin]

The changes were merged into the following branches: main, 18.2.x

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}