From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: nodejs: newer npm?
Date: Thu, 14 Jul 2016 13:55:23 +0200 [thread overview]
Message-ID: <57877DAB.9090906@mlbassoc.com> (raw)
In-Reply-To: <2056819.lo3LDqAOXZ@localhost.localdomain>
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.
>
Are you using AngularJS-1 or AngularJS-2?
> 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
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-07-14 11:55 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
2016-07-13 14:51 ` Gary Thomas
2016-07-14 11:55 ` Gary Thomas [this message]
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=57877DAB.9090906@mlbassoc.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.