-
My issue is different from the one discussed at #3961, so I apologize for opening a new discussion. It looks that the shims have been properly added to the PATH, but their behavior is not as expected. Here are the details(Git Bash): admin MINGW64 ~/AppData/Local/mise/shims
$ echo $PATH
...:/c/Users/admin/AppData/Local/mise/shims:...
admin MINGW64 ~/AppData/Local/mise/shims
$ mise x -- node -v
v20.18.1
admin MINGW64 ~/AppData/Local/mise/shims
$ node -v
bash: node: command not found
admin MINGW64 ~/AppData/Local/mise/shims
$ mise use -g node@20
mise C:\Users\admin\.config\mise\config.toml tools: [email protected]
admin MINGW64 ~/AppData/Local/mise/shims
$ node -v
bash: node: command not found
At the same time, when triggering git hooks (such as pre-commit), I am also unable to use the node command. I suspect it may be the same issue. Please help me, thank you very much! mise doctor:$ mise doctor
version: 2025.1.7 windows-x64 (78bb4fd 2025-01-15)
shims_on_path: yes
build_info:
Target: x86_64-pc-windows-msvc
Features: DEFAULT, NATIVE_TLS, OPENSSL
Built: Wed, 15 Jan 2025 01:54:18 +0000
Rust Version: rustc 1.83.0 (90b35a623 2024-11-26)
Profile: release
shell:
(unknown)
dirs:
cache: ~\AppData\Local\Temp\mise
config: ~\.config\mise
data: ~\AppData\Local\mise
shims: ~\AppData\Local\mise\shims
state: ~\.local\state\mise
config_files:
~\.config\mise\config.toml
ignored_config_files: (none)
backends:
aqua
asdf
cargo
core
dotnet
gem
go
npm
pipx
spm
ubi
vfox
plugins:
toolset:
core:[email protected]
core:[email protected]
path:
~\bin
D:\apps\Git\mingw64\bin
D:\apps\Git\usr\local\bin
D:\apps\Git\usr\bin
D:\apps\Git\usr\bin
D:\apps\Git\mingw64\bin
D:\apps\Git\usr\bin
~\bin
C:\Program Files (x86)\Common Files\Oracle\Java\javapath
D:\apps\ImageMagick
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0
C:\Windows\System32\OpenSSH
C:\Program Files\PowerShell\7
D:\apps\Git\cmd
C:\Program Files\dotnet
C:\Python27
D:\apps\Neovim\bin
~\AppData\Local\mise\installs\bun\1.1.43\bin
~\AppData\Local\mise\installs\node\20.18.1
D:\caches\rust\.cargo\bin
D:\caches\.vm\versions\miniconda_versions\miniconda\condabin
~\.vm
D:\caches\yarn\current\global\node_modules\.bin
~\scoop\apps\yarn\current\bin
~\scoop\shims
~\AppData\Local\Microsoft\WindowsApps
~\AppData\Local\Microsoft\WinGet\Packages\Schniz.fnm_Microsoft.Winget.Source_8wekyb3d8bbwe
D:\apps\Microsoft VS Code\bin
D:\apps\Neovim\bin
~\AppData\Local\fnm_multishells\21080_1719211474792
D:\apps\ffmpeg-7.0.1\bin
~\AppData\Local\Microsoft\WinGet\Packages\ajeetdsouza.zoxide_Microsoft.Winget.Source_8wekyb3d8bbwe
~\AppData\Local\Microsoft\WinGet\Packages\junegunn.fzf_Microsoft.Winget.Source_8wekyb3d8bbwe
D:\apps\Nmap
D:\apps\Git\usr\bin\vendor_perl
D:\apps\Git\usr\bin\core_perl
env_vars:
(none)
settings:
No problems found |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
There is already an open issue/PR around this. Several problems exists in case of Git Bash on Windows. The |
Beta Was this translation helpful? Give feedback.
There is already an open issue/PR around this. Several problems exists in case of Git Bash on Windows. The
mise activate bash
does not generate the correct paths for.bashrc
(C:\Path\To\Program instead of /c/Path/To/Program). Same issue exists for exposing tools toPATH
. When using shims, the fact that they use a.cmd
extension interfers with Git Bash and Cygwin. There is a command_not_found_hook that can be setup to work around this.