[Openembedded-architecture] Improving Node.js developer workflow

[Paul Eggleton]

On Tue, 15 Nov 2016 20:13:53 Esquivel, Benjamin wrote:
> Hello Henry,
> 
> 
> > -----Original Message-----
> > From: openembedded-architecture-bounces at lists.openembedded.org
> > [mailto:openembedded-architecture-bounces at lists.openembedded.org]
> > On Behalf Of Bruce, Henry
> > Sent: Tuesday, November 15, 2016 1:12 PM
> > To: openembedded-architecture at lists.openembedded.org
> > Subject: [Openembedded-architecture] Improving Node.js developer
> > workflow
> > 
> > I have a proposal for a theme for Yocto Project 2.3 development and it
> > has
> > been suggested that I post to this mailing list. In short it's about
> > making life
 easier for Node.js developers by enhancing devtool and its
> > supporting tools (e.g. recipetool). The rationale behind this proposal
> > can be found at https://wiki.yoctoproject.org/wiki/Nodejs_Work
> > flow_Improvements which also includes more details on the proposal and
> > some opens.
> 
> I think Node.js is projected strong in the IoT industry and it theoretically
> fills the gap better than other programming languages when it comes to
> expected IoT market size. I support your point.
> > 
> > I'd appreciate feedback on whether people think that Node.js merits this
> > attention. I'd also be interested to know what level usage drives the
> > transition of recipes from meta-oe into core.
> 
> I have a question here, what do you think as the acceptance criteria for the
> Node.js developer workflow looks like? I'll throw in one obvious point:
> - it is possible for IoT developers to create Yocto Project images with
> Node.js support. 

s/Yocto Project/OpenEmbedded/

Yes we do need some goals, but FYI it is already possible to generate an image 
containing nodejs, that has been possible for some time. I think the main 
areas for development are around what we provide to help developers beyond the 
runtime i.e. in the SDK or on the target. Henry's page (whose URL I will quote 
because it was broken over two lines in the original email) has some 
issues/suggestions in it:

https://wiki.yoctoproject.org/wiki/Nodejs_Workflow_Improvements

One thing I would really like to see at minimum is a single place to get 
nodejs, instead of the 3+ layers that we now have.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre