From: "Davis, Michael" <michael.davis@essvote.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Cc: Gary Thomas <gary@mlbassoc.com>
Subject: Re: nodejs: newer npm?
Date: Wed, 13 Jul 2016 14:41:32 +0000 [thread overview]
Message-ID: <2194432.uJc0j0dgcv@localhost.localdomain> (raw)
In-Reply-To: <57864F34.2010704@mlbassoc.com>
I am building for intel core2-32 with an nginx backend.
I believe the layer exists to keep packages more closely aligned with the
upstream project. I personally use it for the current 6.x releases of nodejs.
On Wednesday, July 13, 2016 04:24:52 PM Gary Thomas wrote:
> On 2016-07-13 15:29, Davis, Michael wrote:
> > I am currently using angular from a different meta layer.
> > https://github.com/imyller/meta-nodejs
> > It maintains newer versions of nodejs.
> > It might be something you want to try.
>
> I have tried this and yes, the versions are newer, but my simple example
> still does not work :-(
>
> What target/platform are you using?
> Any idea why there is a separate layer for something that is in a
> more mainstream (meta-oe) layer for the same things?
>
> > On Wednesday, July 13, 2016 10:11:05 AM Gary Thomas wrote:
> >> On 2016-07-13 09:39, Gary Thomas wrote:
> >>> The current (at least 4.4.4) nodejs recipe also creates nodejs-npm
> >>> which is npm version 2.15.1. I'm trying to run angularjs that needs
> >>> npm >= 3.3.x. I've not yet tried the update to 4.4.5, so if this
> >>> fixes the issue just let me know.
> >>>
> >>> What needs to be done to get a newer npm?
> >>>
> >>> BTW, the current one segfaults when trying to install the
> >>> attached package file.
> >>
> >> I have now tried nodejs-4.4.5 which has npm-2.15.5 It no longer
> >> segfaults on the install step, but it doesn't really work :-(
> >> Any access just returns 'Cannot GET /'
> >>
> >> Anyone have suggestions on how I might debug this? It's a known
> >> working (simple) application I got from
> >> https://angular.io/docs/ts/latest/quickstart.html
next prev parent reply other threads:[~2016-07-13 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 7:39 nodejs: newer npm? Gary Thomas
2016-07-13 8:11 ` Gary Thomas
2016-07-13 13:29 ` Davis, Michael
2016-07-13 14:24 ` Gary Thomas
2016-07-13 14:41 ` Davis, Michael [this message]
2016-07-13 14:51 ` Gary Thomas
2016-07-14 11:55 ` Gary Thomas
2016-07-14 14:55 ` Davis, Michael
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=2194432.uJc0j0dgcv@localhost.localdomain \
--to=michael.davis@essvote.com \
--cc=gary@mlbassoc.com \
--cc=openembedded-devel@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