Skip to content

Fix MISE executable shim paths for different host environments #36

Open
jasoncomes wants to merge 1 commit intomainfrom
jc/fix-mise-path-descovery-for-vscode-terminal
Open

Fix MISE executable shim paths for different host environments #36
jasoncomes wants to merge 1 commit intomainfrom
jc/fix-mise-path-descovery-for-vscode-terminal

Conversation

@jasoncomes
Copy link
Contributor

After migrating to MISE, our Node dependencies are now managed in a different location. VSCode launch commands (like development mode) run in the integrated terminal, which doesn't automatically know where MISE's executables live. Updated settings.json to include MISE's shim directories in the terminal PATH for macOS, Linux, and Windows.

@jasoncomes jasoncomes force-pushed the jc/fix-mise-path-descovery-for-vscode-terminal branch from ee7f2ef to 30d94bb Compare January 27, 2026 16:44
After migrating to MISE, our Node dependencies are now managed in a different location. VSCode launch commands (like development mode) run in the integrated terminal, which doesn't automatically know where MISE's executables live. Updated settings.json to include MISE's shim directories in the terminal PATH for macOS, Linux, and Windows.
@jasoncomes jasoncomes force-pushed the jc/fix-mise-path-descovery-for-vscode-terminal branch from 30d94bb to b6d2d50 Compare January 28, 2026 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant