On Windows operating systems, environment variables are case-insensitive.

• https://nodejs.org/api/process.html#processenv

I read that too, however it doesn't seem to always be the case for all env vars:

PS C:\dev\bfp-app\packages\app> node -v    
v16.19.1
PS C:\dev\bfp-app\packages\app> npm -v     
9.5.1

I don't normally develop on windows, so this is on a fresh installation of w11 on a VM too

Then open an issue on Node.js and add a code comment above your code change with a link to the Node.js issue. I prefer to only add workarounds when there's a chance it will be fixed properly at some point.

No problem, thanks anyway

Why are you closing?

Why are you closing?

I'm unable to consistently reproduce this in a blank sandboxe, so I'm assuming that it must be some combination of our code and environment causing this as opposed to node or otherwise. If I find a more consistent reproduction in node, I'll re-open with an issue, until then I'm going to assume it's a me problem :)