Nodejs Workflow Improvements: Difference between revisions
From Yocto Project
Jump to navigationJump to search
Henry Bruce (talk | contribs) |
Henry Bruce (talk | contribs) |
||
| Line 3: | Line 3: | ||
== Typical Workflow Assumption == | == Typical Workflow Assumption == | ||
Typical workflow involves tinkering with npm on the target and then locking down once app is working. | |||
== Proposals and Opens == | == Proposals and Opens == | ||
Revision as of 22:04, 14 November 2016
Summary
Node.js is a popular JavaScript runtime environment that is becoming popular among IoT developers. We propose that Yocto Project be enhanced to better support the typical Node.js workflow.
Typical Workflow Assumption
Typical workflow involves tinkering with npm on the target and then locking down once app is working.
Proposals and Opens
- Clarify rationale for mutliple nodejs layers: meta-oe, meta-nodejs, meta-intel-iot-middleware
- 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.
