When I fainted on a crowded bus i Buenos Aires (as a tourist from Sweden) the bus driver stoped to check on me. When I wanted to get off and rest a while, two other passengers got off the bus with me to make sure I was okay.
I'm sure there must be more instances, but that's the first one I can think of.
There are a few things I think you could do about it:
1. Find somewhere to work were they use a tech stack you feel is more appropriate.
2. Work at a smaller company where you have more say in the tech stack and tooling.
3. Find a company or team where someone else works on developer tooling and automation, so you only need to worry about site building.
4. Freelance and specialise in what you enjoy working with.
I work at a small (15 people) web agency where I have a large say in what we use. It's surprisingly little React/Vue, a bit of WordPress (not everyones favourite maybe) and a lot of backend work on APIs and admins in Laravel and plain PHP/HTML with some vanilla JS. Only about 10 percent of the clients ever care what stack we use.
All of our 60+ projects are setup the same way:
1. Pull down the repo and run "docker compose up" to start you local environment. Any composer or npm commands should be run through docker compose, so no local installs (except docker) are needed.
2. Push to staging branch to deploy to staging and merge to production branch to deploy to production.
I would still say that, to most people, a startup implies more than just a newly started business. I have never seen or heard someone who has just started a small brick and mortar business (without grandiose expansion plans) refer to it as a startup.
That said, I'm not a native english speaker and I don't live in US - maybe it's more common than I think.
I think Graham's definition aligns much better with general usage of the word than a definition that would make the new ice cream stand at the corner a startup.
I'm sure there must be more instances, but that's the first one I can think of.