I think the boring stack would skip the need for most of these. That is 5 different tools to write TypeScript in order to get some HTML, CSS and JavaScript for things that are not covered by modern web standards. Not including the frameworks itself which mostly have the same goal.
Yes, if your goal is to get HTML/CSS/JS in any form to a web client then you don't need this stuff.
If your goal is to ship a web app that stands a chance of surviving multiple devs, production traffic, etc then you need more tools. Testing behavior (vitest), enforcing code standards (oxfmt and oxlint), optimizing network calls (e.g. tree shaking from Rollup), etc. all go beyond what you describe.
This stack is as boring as it gets without literally using the tools it consolidates and replaces or dropping a requirement that necessitates them.