View source for Nodejs Workflow Improvements

== Summary ==
Many industry pundits predict that IoT will not be built by traditional C/C++ embedded developers as there just aren't enough of them to go around. The 2016 Stack Overflow developer survey shows JavaScript to be the most popular language. [https://en.wikipedia.org/wiki/Node.js Node.js] is a popular JavaScript runtime environment. These two data-points indicate that Node.js is likely to become increasingly popular among IoT developers. The Yocto Project has some support for [[TipsAndTricks/NPM|npm project packaging]], but can be enhanced to better support the typical Node.js workflow.

== Workflow Assumption ==
Typical workflow involves tinkering with npm on the target and then locking down once app is working.

== Proposals and Opens ==
* Comprehend Node.js LTS and decide what version we support
* Move nodejs into openemebdded core?
* Should we create a node.js category in Bugzilla ?
* Create image for node development (core-image-nodejs) with node and npm (and what else?)
* Once project is working on target, how do we package it. devtool cleverness that sucks files from target?
* Extend devtool to handle multiple layers to help structure complex projects

== Tasks in Bugzilla ==
See [https://bugzilla.yoctoproject.org/showdependencytree.cgi?id=10653&hide_resolved=1 Project Management bug #10653] that has all current Node.js tasks/bugs as dependencies.