💖 Thanks for opening this pull request! 💖
Please be patient and we will get back to you as soon as we can.

If I understand correctly, we automatically add all fields from package.json to env variables. If that is the case, we need to check what field does npm include and use the same list.

I believe it happens in this function: https://github.com/pnpm/npm-lifecycle/blob/1e0f149176877f906968a01087cf63290652ccbc/index.js#L347

See all the env variables created with the npm_package_ prefix. We should find how npm does it. Probably it has an allowlist of fields.

@zkochan I will dig into that, thanks!

It looks like it is here:

https://github.com/npm/cli/blob/6ca609e20b68fb2e5ef8177db116b84a339461fd/workspaces/arborist/lib/arborist/rebuild.js#L311-L320

I also verified that on my Windows box that those are the only npn_package_ prefixed env variables I see when a script is run

There is an RFC about this change in npm CLI: https://github.com/npm/rfcs/blob/5f53b903b4b92881a9b7fc73e2994c33e419975c/implemented/0021-reduce-lifecycle-script-environment.md