Nodejs Workflow Improvements

From Yocto Project
Jump to navigationJump to search

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.
  • Open:

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

These are higher level tasks (may not be a 1:1 mapping for entries in Bugzilla)

  • Give more developer feedback on progress during lengthy tasks
  • Simplify deployment with devtool - node (and npm?) should be automatically deployed if not already on target
  • Enable development on target and then devtool encapsulates resulting node.js project into package
  • Add devtool support for multiple layers to help structure complex projects
  • Everything else is in Bugzilla