From: Trevor Woerner <twoerner@gmail.com>
To: "Davis, Michael" <michael.davis@essvote.com>
Cc: ilkka.myller@nodefield.com,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: Broken NPM builds
Date: Wed, 26 Apr 2017 15:28:15 -0400 [thread overview]
Message-ID: <20170426192815.GA2366@linux-uys3> (raw)
In-Reply-To: <655290B7709079438B7932553958E60D16D23684@ESS-EX01.essvote.corp.local>
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 this issue.
There's been quite a bit of churn on master this cycle, it's not too
surprising master is struggling. Any chance you can share your recipe; or a
stripped-down, "example.com" version of your recipe so others can take a look?
> On a related side note I have recipes working for node 6.10.2.
You have a grunt-cli recipe working on master with node 6%?
> Is there a reason we are staying on the 4.x series now that 6 is LTS?
I'm guessing nobody got around to noticing the switch. I guess we could
cherry-pick node-6% from
https://layers.openembedded.org/layerindex/branch/master/layer/meta-nodejs/
Ideally we'd either merge all/most of
https://layers.openembedded.org/layerindex/branch/master/layer/meta-nodejs/
into oecore, or remove what's in oecore and tell people to use the external
layer. Why does oe-core have some, but not all, node support?
next prev parent reply other threads:[~2017-04-26 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 16:01 Broken NPM builds Davis, Michael
2017-04-26 19:28 ` Trevor Woerner [this message]
2017-04-26 19:43 ` Davis, Michael
2017-04-26 20:31 ` Ilkka Myller
2017-04-27 9:52 ` Alexander Kanavin
2017-04-27 9:56 ` Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170426192815.GA2366@linux-uys3 \
--to=twoerner@gmail.com \
--cc=ilkka.myller@nodefield.com \
--cc=michael.davis@essvote.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox