Add pnpm global packages support

[dougg0k]

Hi,

Could you add support for installing global packages using pnpm?

e.g.,

[tools]
...
pnpm = 'latest'
"pnpm:typescript" = 'latest'

Currently only npm seems supported. https://mise.jdx.dev/dev-tools/backends/npm.html#usage

Thanks.

[risu729]

Using Bun to install npm backend tools is supported.
https://mise.jdx.dev/dev-tools/backends/npm.html#npm.bun

Do you have any reasons why you want to use pnpm?

[dougg0k]

It would not make sense, as both npm and pnpm tries to do the same thing. It should need something separated. I suppose even for bun.

This would make sense to be together with the tool installation, not based on npm.

---

As for the pnpm global.

You already provide the option to install the tool itself, which may or may not set the PNPM_HOME variable and then set it to PATH. That is already enough for global packages.

❯ $env.PNPM_HOME                                                                                                                                                                                           
/home/user/.local/share/pnpm

❯ whereis tsc                                                                                                                                                                                              
tsc: /home/user/.local/share/pnpm/tsc

❯ tsc --help                                                                                                                                                                                               
tsc: The TypeScript Compiler - Version 5.8.3

You could add a constraint, only support global packages install if the tool used, are installed through mise.

[risu729]

Just to clarify, the backend feature is designed to install executable tools.
Whether a tool like tsc is installed using npm, pnpm, or bun, the end result is the same: an executable available via mise.

The npm.bun backend depends on both npm and bun because Bun does not provide an alternative to npm view.
However, like pipx/uvx, using pnpm alone should be enough to support the npm backend.
It does not require the npm CLI to install packages like npm:typescript using pnpm.

In this case, the backend is named npm because it installs tools from the npm registry, but it doesn't need the npm command itself.

The options, such as npm.bun or npm.pnpm, mainly affect installation speed, not the behaviour of the installed tool.

While temporarily setting PNPM_HOME or adding something like ./test/bin to PATH during installation might work, I think it would be complex.

[LandonSchropp]

@risu729 Any chance you might reconsider this? I recently ran into this after migrating from Bun to Node.js/pnpm due to issues with bun test. I agree with @dougg0k that pnpm is the best package manager for Node.js right now.

[jdx]

@LandonSchropp if you'd like to see it, work up a PR. Don't ask @risu729 to do it for you.

[LandonSchropp]

@jdx Fair enough.

[risu729]

The latest mise supports using pnpm instead of npm. #7214

[dougg0k]

Maybe the setting should be named js.package_manager rather than npm.package_manager #7214, same for the prefix e.g., "js:typescript" = "latest", or actually use "node" for node packages, otherwise deno or bun for their respective global packages. But dont matter much.

[dougg0k]

I checked, some packages seems to also be included where pnpm are located, yet, others do not.

✗ whereis npq                                                                                                                                                                                                                                                                      
npq: /home/user/.local/share/mise/installs/npm-npq/3.15.4/bin/npq

❯ whereis tsc                                                                                                                                                                                                                                                                      
tsc: /home/user/.local/share/mise/installs/npm-typescript/5.9.3/bin/tsc /home/user/.local/share/pnpm/tsc

Even though tsc/typescript are not longer globally installed through pnpm.

[risu729]

Maybe the setting should be named js.package_manager rather than npm.package_manager #7214, same for the prefix e.g., "js:typescript" = "latest", or actually use "node" for node packages, otherwise deno or bun for their respective global packages. But dont matter much.

The prefix is named after the "npm backend", and I don't think we need to rename the whole thing.

[risu729]

I checked, some packages seems to also be included where pnpm are located, yet, others do not.

✗ whereis npq                                                                                                                                                                                                                                                                      
npq: /home/user/.local/share/mise/installs/npm-npq/3.15.4/bin/npq

❯ whereis tsc                                                                                                                                                                                                                                                                      
tsc: /home/user/.local/share/mise/installs/npm-typescript/5.9.3/bin/tsc /home/user/.local/share/pnpm/tsc

Even though tsc/typescript are not longer globally installed through pnpm.

Isn't /home/user/.local/share/pnpm/tsc coming from the usual pnpm global install, like pnpm add --global?
I think in a clean environment mise only installs tools in ~/.local/share/mise/installs/npm-....

[dougg0k]

~ as 🧙 took 51s
❯ whereis tsc                                                                                                                                                                                                                                                                      
tsc: /home/user/.local/share/mise/installs/npm-typescript/5.9.3/bin/tsc /home/user/.local/share/pnpm/tsc

~
❯ pnpm list -g                                                                                                                                                                                                                                                                     

~
❯

tsc are in fact located in the folder, just dont know why. No problem I guess.

[dougg0k]

Hey @risu729

I just did a mise upgrade here and I had some nodejs global packages upgrade.

I have pnpm as the default package manager.

[settings.npm]
package_manager = "pnpm"

But, in the update, none were the npm itself, yet I got a message that only appears when installing stuff through the npm tool (not the backend). There might be a bug on the implementation, so it's not using pnpm.

mise WARN  Error getting latest version for yarn: error running list-all: exited with code 1
error: git-remote-https died of signal 11
fatal: remote helper 'https' aborted session
npm notice
npm notice New minor version of npm available! 11.6.2 -> 11.7.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.7.0
npm notice To update run: npm install -g [email protected]
npm notice
npm notice
npm notice New minor version of npm available! 11.6.2 -> 11.7.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.7.0
npm notice To update run: npm install -g [email protected]
npm notice
npm notice
npm notice New minor version of npm available! 11.6.2 -> 11.7.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.7.0
npm notice To update run: npm install -g [email protected]
npm notice
npm notice
npm notice New minor version of npm available! 11.6.2 -> 11.7.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.7.0
npm notice To update run: npm install -g [email protected]
npm notice
 ███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████mise 2025.12.12 by @jdx█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████    8s
Upgraded 2 tools:
  npm:@github/copilot 0.0.371 → 0.0.372
...

The yarn error above I already reported in another discussion #4218

❯ mise -v  
              _                                        __
   ____ ___  (_)_______        ___  ____        ____  / /___ _________
  / __ `__ \/ / ___/ _ \______/ _ \/ __ \______/ __ \/ / __ `/ ___/ _ \
 / / / / / / (__  )  __/_____/  __/ / / /_____/ /_/ / / /_/ / /__/  __/
/_/ /_/ /_/_/____/\___/      \___/_/ /_/     / .___/_/\__,_/\___/\___/
                                            /_/                 by @jdx
2025.12.12 linux-x64 (2025-12-18)

[dougg0k]

But it does.

❯ npm info typescript 

[email protected] | Apache-2.0 | deps: none | versions: 3659
TypeScript is a language for application scale JavaScript development
https://www.typescriptlang.org/

keywords: TypeScript, Microsoft, compiler, language, javascript

bin: tsc, tsserver

dist
.tarball: https://registry.npmjs.org/typescript/-/typescript-5.9.3.tgz
.shasum: 5b4f59e15310ab17a216f5d6cf53ee476ede670f
.integrity: sha512-jl1vZzPDinLr9eUt3J/t7V6FgNEw9QjvBPdysz9KfQDD41fQrC2Y4vKQdiaUpFT4bXlb1RHhLpp8wtm6M5TgSw==
.unpackedSize: 23.6 MB

maintainers:
- microsoft1es <[email protected]>
- typescript-bot <[email protected]>
- weswigham <[email protected]>
- andrewbranch <[email protected]>
- typescript-deploys <[email protected]>
- jakebailey <[email protected]>

dist-tags:
latest: 5.9.3                            next: 6.0.0-dev.20251219                 rc: 5.9.1-rc                             beta: 5.9.0-beta                         insiders: 4.6.2-insiders.20220225        tag-for-publishing-older-releases: 4.1.6 dev: 3.9.4

published 2 months ago by typescript-bot <[email protected]>

~
❯ pnpm view typescript 

[email protected] | Apache-2.0 | deps: none | versions: 3659
TypeScript is a language for application scale JavaScript development
https://www.typescriptlang.org/

keywords: TypeScript, Microsoft, compiler, language, javascript

bin: tsc, tsserver

dist
.tarball: https://registry.npmjs.org/typescript/-/typescript-5.9.3.tgz
.shasum: 5b4f59e15310ab17a216f5d6cf53ee476ede670f
.integrity: sha512-jl1vZzPDinLr9eUt3J/t7V6FgNEw9QjvBPdysz9KfQDD41fQrC2Y4vKQdiaUpFT4bXlb1RHhLpp8wtm6M5TgSw==
.unpackedSize: 23.6 MB

maintainers:
- microsoft1es <[email protected]>
- typescript-bot <[email protected]>
- weswigham <[email protected]>
- andrewbranch <[email protected]>
- typescript-deploys <[email protected]>
- jakebailey <[email protected]>

dist-tags:
latest: 5.9.3                            next: 6.0.0-dev.20251219                 rc: 5.9.1-rc                             beta: 5.9.0-beta                         insiders: 4.6.2-insiders.20220225        tag-for-publishing-older-releases: 4.1.6 dev: 3.9.4

published 2 months ago by typescript-bot <[email protected]>

[risu729]

It does, but internally it just calls npm.

[dougg0k]

It seems like so. Question is, if npm are not installed, does it still work. That could prevent the npm outdated notices.

[risu729]

Hmm I don't think so, but I need to check it later.

[dougg0k]

npm config set update-notifier false
npm config set fund false
npm config set audit false

export NPM_CONFIG_UPDATE_NOTIFIER=false
export NPM_CONFIG_FUND=false
export NPM_CONFIG_AUDIT=false