Add node.js support

[hohwille]

We already have a ng commandlet for angular-cli. However, without node.js support the user needs to manually install node.js into his system/path. This is not consistent with our approach and expected UX of devon-ide.

Hence we need to add a node commandlet. This whould then be able to download and install node.js. We need to check if we want to use node version manager or manage the node version on our own.

[sjimenez77]

IMHO we should use always the latest LTS node version. nvm is really good (I use it) but adds a bit of complexity to be maintained alongside with the node.js versions. Besides, we are focusing lately in the yarn package manager, so we should also provide it just in case you want to use in your node.js front and/or backend projects.

In the latest devonfw distributions we managed to install a portable version of the latest node.js LTS in the software folder. We should do something similar or at least discuss if we can ask the user to install it globally in the system. It will be definitely more natural to any frontend developer.

My concern is how to handle everything in the future devonfw dashboard. For the moment we are struggling a lot calling efficiently bash scripts. I can imagine that we will also need to provide some kind of feature selector that will check and install the latest versions of java, node.js, our IDEs, stacks, etc.

[hohwille]

@sjimenez77 thanks for your valuable feedback. I agree that using LTS version of node is great.
However, I think that the general idea of devon-ide is:

• keep the prerequesites as little as possible
• make the IDE as local as possible and prevent global installations that cause conflicts between co-existing projects.

Hence, if possible I would still suggest that we do the same for node as we do for all the other tools which is download and "install" them locally within the IDE.
This does not necessarily require that one has to call wrapper bash scripts to launch node, npm, yarn, etc. (if that actually was the fear you were having, I am not sure if otherwise I got your concern right). For the "feature selector" I also do not get your point. People just call the setup script once (what is technically nothing more than devon ide setup). This installs all the tools reuqired by the project where now each project is free to customize and configure the tools they need in their settings. So projects not using JavaScript/TypeScript/node.js/npm/yarn/etc. do not care about all this. However, most projects will require it as we assume and what is currently the default. The only problem ist that I have not implemented this for node as I am not an experienced JavaScript/Client guy so I would need some contribution.

[hohwille]

Implemented with PR #138 and tested on mac OS.
If you do not like the default version or find a bug for other OS, please provide PR.