Skip to content

fix: set path variables when trying to run npm commands #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 4, 2025
Merged

fix: set path variables when trying to run npm commands #61

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions Editor/Utils/McpUtils.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -353,6 +353,11 @@ public static void RunNpmCommand(string arguments, string workingDirectory)
// Fallback to /bin/bash to find 'npm' in PATH
startInfo.FileName = "/bin/bash";
startInfo.Arguments = $"-c \"npm {arguments}\"";

// Ensure PATH includes common npm locations and current PATH
string currentPath = Environment.GetEnvironmentVariable("PATH") ?? string.Empty;
string extraPaths = "/usr/local/bin:/opt/homebrew/bin";
startInfo.EnvironmentVariables["PATH"] = $"{extraPaths}:{currentPath}";
}

try
Expand Down