Set npm_config_user_agent when running pnpx and pnpm create

[cyco130]

• I'd be willing to implement this feature (contributing guide)

Describe the user story

In create-* packages one often wants to install npm dependencies at the end of project initialization. But this requires determining the preferred package manager of the user. Most packages add a CLI option or prompt for this purpose. But the user has already expressed their choice buy running npm init, yarn create, or pnpm create (or init, or pnpx create-* etc.). We could determine the package manager choice if there was a way to determine the package manager that launched the create-* script.

Describe the solution you'd like

npm and yarn set the npm_config_user_agent environment variable under these circumstances but pnpm doesn't. The problem would be solved if it did. The inconsistency with the other package managers even suggests that it may simply be a bug and not a missing feature.

Describe the drawbacks of your solution

None I can think of.

Describe alternatives you've considered

There are no alternatives I can think of but asking the user explicitly for their package manager preference.

[bestickley]

Thank you @cyco130 for raising this.
Here is a relevant SO post for others who are curious: https://stackoverflow.com/questions/68133683/is-there-a-cross-platform-way-to-get-the-name-of-the-parent-process-in-node-js

[cyco130]

@bestickley Heh, that's also me 😁

[bestickley]

😆 well, thank you again!

[zkochan]

Not sure why it is not set when pnpm init runs. We set it for sure in pnpm run and pnpm install. We should fix this.

[vhscom]

tauri users desiring to use pnpm could get a better dx when this is fixed. not exactly a game-changer but it's a rough edge affecting some external integrations which could help increase traction if fixed.

[vhscom]

damn that was quick work. nice job. 👌