You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
I had trouble to install some extensions on OSX. The problem was that the node command wasn't found.
I think the problem is the executable name of node process of Brackets: on Windows is node.exe, and on Windows 10 I don't have any problem, while on macOS and Linux is Brackets-node.
I don't have proof this is the real problem but to my eyes seems very likely.
On #10658 there were some discussion to rename the process on Windows. Maybe we should instead rename the others?
Steps to Reproduce
Go to the extension manager
Try to install the npm registry extension
Expected behavior: the extension should be installed
Actual behavior: the installation fails
Versions
OSX
1.9
The text was updated successfully, but these errors were encountered:
Description
I had trouble to install some extensions on OSX. The problem was that the
node
command wasn't found.I think the problem is the executable name of node process of Brackets: on Windows is
node.exe
, and on Windows 10 I don't have any problem, while on macOS and Linux isBrackets-node
.I don't have proof this is the real problem but to my eyes seems very likely.
On #10658 there were some discussion to rename the process on Windows. Maybe we should instead rename the others?
Steps to Reproduce
Expected behavior: the extension should be installed
Actual behavior: the installation fails
Versions
OSX
1.9
The text was updated successfully, but these errors were encountered: