On 04/26/2017 11:31 PM, Ilkka Myller wrote:
This design allows building static, immutable, OE-proper packages for
Node.js based applications while still using standard npm installation
process on the build host. This is where OE core npm class differs the
most by-design.
But are they
On 04/26/2017 11:31 PM, Ilkka Myller wrote:
This design allows building static, immutable, OE-proper packages for
Node.js based applications while still using standard npm installation
process on the build host. This is where OE core npm class differs the
most by-design.
But are they
I’m the maintainer of meta-nodejs layer. The layer offers latest Node.js
versions (current, LTS and end-of-life). As a member of Node.js core
collaborator team, I’ve picked up the task of maintaining up-to-date Node.js
offering for OE.
In addition to Node.js core packages the layer offers
riginal Message-
From: Trevor Woerner [mailto:twoer...@gmail.com]
Sent: Wednesday, April 26, 2017 2:28 PM
To: Davis, Michael
Cc: openembedded-core@lists.openembedded.org; ilkka.myl...@nodefield.com
Subject: Re: [OE-core] Broken NPM builds
On Wed 2017-04-26 @ 04:01:20 PM, Davis, Michael wrot
On Wed 2017-04-26 @ 04:01:20 PM, Davis, Michael wrote:
> I have a simple grunt-cli recipe using inherit npm.
> On master branch it appears to be broken and unable to find the registry.
> Same recipe on Morty branch works fine.
> I looked through the mailing list and didn't see anyone else seeing
I have a simple grunt-cli recipe using inherit npm.
On master branch it appears to be broken and unable to find the registry. Same
recipe on Morty branch works fine.
I looked through the mailing list and didn't see anyone else seeing this issue.
On a related side note I have recipes working for
