[
https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-21005:
----------------------------------------
And for the record, here are my suggestions how we could improve it:
1. Look through the system path and find the node js binary. It should be very fast so I
suggest do it when we reset the preference to default setting (but make sure we can't
block UI here or something)
2. Look for npm and bower using the system path for Mac and Linux. For Windows look for
either npm-cli.js or npm.cmd whatever is easier. Windows code should be smart enough to
distinguish one from another and use "/path/to/node.exe /path/to/npm.cli.js" or
"/path/to/npm.cmd" depending on the preference setting for the npm bin file.
Node / Bower / npm location should point to the node executable file
instead of the parent folder of it
-------------------------------------------------------------------------------------------------------
Key: JBIDE-21005
URL:
https://issues.jboss.org/browse/JBIDE-21005
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: javascript, nodejs
Affects Versions: 4.3.0.Final
Reporter: Alexey Kazakov
Assignee: Ilya Buziuk
Fix For: 4.4.0.Alpha1
Window->Preferences->Java Script tools->Node
It's confusing that "Node Location" in that preference page is actually
references to the parent folder of the executable node file. I would expect
"/usr/bin/nodejs" or "C:/.../node.exe" in that field.
IMO it's confusing and actually not very flexible. Why wouldn't let users to
select the executable file itself?
WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)