proto: Inconsistency between tool installation

What version?

0.21.0

Which command?

No response

What happened?

How proto installs and refers to various executables is confusing and inconsistent:

node exists as a bin symlink and a global shims script. npm exists as a bin symlink but NOT a global shims.

proto bin node and proto bin node --shim both show the versioned node executable .proto\tools\node\20.9.0\node.exe. proto bin npm shows me the versioned node .proto\tools\npm\10.1.0\bin/npm-cli.js and proto bin npm --shim shows me a powershell script .proto\tools\npm\10.1.0\shims\npm.ps1

proto bin npm shows the path to the current npm. proto bin npx fails with “npx is not a built-in tool or has not been configured as a plugin, unable to proceed.”

Any logs?

No response

Operating system?

Windows

Architecture?

x64

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Comments: 17 (17 by maintainers)

Most upvoted comments

I’ve updated the docs a bit to clarify the terminology.

This should be much more straight forward now in 0.22.