Can you believe it? pnpm <scriptname> goes through this bizarre
anti-logic wrt. running scripts.
If the script is a dedicated pnpm command, it will run that command.
Else if the script exists in package.json, it will run it.
At this point, it then tries to run it as a normal shell command. By
checking if <scriptname> is in $PATH and then executing that.
What the hell? This was helpfully revealed to my by a tester who found
`pnpm sort` was taking too long. That's because it was running
`sort(1)`.
Absolutely insane behaviour. Why???
unicode maintains two star icons and only
one of them is properly supported on certain devices
huge pain because my editor and browser renders them
properly. wonderful.
I have absolutely no idea why this is like this. It does not
make any sense, so I am inclined to believe it is some sort of bug
with pnpm and workspaces.
ah well.
These are actually necessary in non-dev scenarios, as we use
ts-node/register as our loader. This expects types to exist
for our dependencies, for some reason.
I'm too tired to properly resolve this, so making @types mandatory
is my hack fix.
It's not like they add much to the build size anyway.
this might be a footgun in the future, who knows.
I feel like having a dedicated button for "deploy" disguised as "run
workflow" might result in an accidental deploy. ah well.
they're wrong, by the way. they don't analyse lockfiles but instead
analyse package.jsons. I mean, they could be correct in theory, but this
is why we have lockfiles right?
Dependabot can shut the hell up. Support PNPM. Please!
zkldi