I should just quit. I am not paid enough to deal with this pissing contest.
Reviewer:
Need to add instructions (on readme) for installing pnmp, or if possible, have the top-level npm i install it (lol).
Also, it looks like we are no longer using lerna? If that's right, let's remove the dependency; its dependencies give some security audit messages at install.
Me:
it's good enough for now. Added a new ticket to resolve package manager confusions. (Migrate to pnpm workspaces)
Reviewer:
I will probably be responsible for automating deployment of this (I deployed the webapp on cloudflare pages and there is no work that needs to be done. "automating deployment" literally means replacing npm with pnpm). I disagree that it's good enough for now.

Imagine all readmes on github document how to install yarn/pnpm.

Lesson learned:
If you think an OOP static site developer can't handle modern JS framework, you are probably right.

Thought to let you folks know who doesn't know about `pnpm`.
• no duplication of libraries. Second time the libs will be symlinked
• you can alias a library and it's separate versions.
• blazing fast.
• almost feels like python's package manager.

I can work with Angular, even though it's pain in the but.
My current Angular job is actually the job with the first manager that had decent human values and ethics, I like my team, and yeah, what we building is shit. But it's only 30% shit because of Angular, another 30% are due to SAFe, and the rest is the usual stuff.
Still enjoy my job and respect my team.

But please do not expect me to pretend Angular is on a comparable level to React. Angular hasn't brought any actual innovation in most major versions but releases those breaking major updates still at least twice a year.
Ivy might be awesome, but only because Angular told the world 3 years ago also to have Ivy compatible compile targets for their libs/packages doesn't mean everybody cared.
And the ngcc, the awesome compatibility compiler, mutates node modules in place. So ne parallel stuff, no using yarn2 or pnpm.
At the same time, React brought so many innovations into the frontend world but is basically backwards compatible.

Not sure how the Angular partial compilation and whatever needs to go on works, but it seems like there's hardly anyone that really knows, so you can't use Vite or whatever other new tool.
And sure, if you're really good, you can write Angular without producing memory leaks.
But it's really hard. Do you know what's also quite hard: Producing memory leaks with React!

And for sure, Angular Universal, which isn't used by anyone, it feels like, will still be on a comparable level to an open source product that's used all over the world, builds the basis for an open source company, and is improved by thousand of issues day by day.

And sure, two kinds of change detection are a great idea. And yeah, pretending Angular comes with all included makes it worth it that the API is fucking huge and you're better of knowing nothing, because you have to read up things, than knowing quite a lot, since making assumptions and believing apis work in a similar way and follow similar contentions...

Whatever... I work with it. Like the time. Like the company, even my poss. But please don't expect my lying to you this was a good idea, or Angular is even remotely the same level of React.

Vite is a black box that can break at any time, I am starting to hate black boxes. Mix that in with flakey pnpm and node (we should all use deno now).

Good luck if something doesn't work in vite.

Proxy hasn't been working correct for me last 2 days so I ditched it and turned off chrome web security

Does anyone know why those web-dev tools: yarn, npm, npx, pnpm don't have man entries? man isn't probably used much anymore, but not having it makes them appear less serious and mature to me.

Today was the first time I've tried out `pnpm` (after using both `npm` and `yarn` in the past).

It's safe to say that it will also be the last time at least for this year.

The damned thing randomly crashed my builds on `vercel` (which I also set up today for the first time, and which uses `pnpm` by default).

Then, it continued to mess with me by randomly breaking the TSX transpilation locally.

So, it might be the fastest and nicest package manager for the JS world, but it surely shouldn't cause me trouble twice on the same day and get me 2+ hours of debugging.

I wish i had know about pnpm earlier. Would have prevented the gazillion of node module folders spread across my projects