winget install and upgrade experience revision

[Emcho0]

The current winget install pnpm.pnpm installs the pnpm binary in the winget\packages\ directory instead of the usual PNPM_HOME path.

There should be a clear error message saying to run pnpm setup after installing with a package manager of choice if it isn't already done. Also pnpm should be self updated via a project, not globally. For that, the winget upgrade pnpm.pnpm (or pnpm) is for global use cases.

Possible solutions

• Manually do pnpm setup after installing with winget, but it would require removing the PNPM_HOME and reinstalling again.
• When installing via winget, automatically add PNPM_HOME to path.

By implementing these solutions, not only it improves the experience, but it would require less work and suffering for updating pnpm on windows.

[SametDulger]

Hi Emcho0,

Thanks for raising this — the current behavior where winget install pnpm.pnpm places the binary inside the winget packages folder instead of the expected PNPM_HOME can definitely cause confusion.

Your suggestion to provide a clear message prompting users to run pnpm setup after installation would improve onboarding a lot.

Also, automating adding PNPM_HOME to the PATH during installation would reduce manual steps and errors.

Regarding updates, having winget upgrade pnpm.pnpm handle the global use case while encouraging project-local pnpm usage aligns well with modern package management best practices.

Overall, implementing these changes would streamline the Windows pnpm experience significantly.

Have you filed a feature request or bug report on the pnpm or winget repos? It might help get traction on this.

[Emcho0]

I didn't report any issues for this problem.