Nodejs Workflow Improvements: Difference between revisions
From Yocto Project
Jump to navigationJump to search
Henry Bruce (talk | contribs) |
Henry Bruce (talk | contribs) |
||
| Line 2: | Line 2: | ||
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. We propose that Yocto Project be enhanced to better support the typical Node.js workflow. | 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. We propose that Yocto Project 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. | Typical workflow involves tinkering with npm on the target and then locking down once app is working. | ||
Revision as of 18:47, 15 November 2016
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. 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. We propose that Yocto Project 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 Project Management bug #10653 that has all Node.js tasks/bugs as dependencies.
