[
https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi...
]
Ilya Buziuk commented on JBIDE-21005:
-------------------------------------
[~akazakov], sounds good. I also have some suggestions that we can discuss later (will
write it here in order not to forget):
1) We might use ${system_path} for Linux - it seems to work neatly there
2) We might have issues on Mac, cause there might be nothing concrete in system path
(desktop launch case). So we could detect tools in default locations:
- usr/bin
- usr/local/bin
- usr/local/bower
- usr/local/npm
etc..
{quote}
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.
{quote}
Yes, this is a good idea indeed. However, need to think how to implement it neatly and in
a generic way - launching npm / bower *directly* breaks architecture of launching
everything via node (launch that is not depend on path). But I anyways I do believe that
user experience is more important than architecture to a certain extend
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)