Hi all
I just noticed that when I ran npm outdated it said everything was
hunky-dory but in fact some of my packages were out of date. The packages *
were* up-to-date with respect to the versions specified in my package.json
dependencies, but I understood that I could use npm outdated to tell me
Did you try with -g option? Eg: npm -g outdated
Best Regards,
--
Yuri Teixeira
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Thursday, 14 de June de 2012 at 12:38, Graeme Foster wrote:
> Hi all
>
> I just noticed that when I ran npm outdated it said everything was hunky-dory
>
That checks the globally-installed packages, and I would imagine behaves in
the same way.
G.
On Thursday, June 14, 2012 6:06:55 PM UTC+1, Yuri Teixeira wrote:
>
> Did you try with -g option? Eg: npm -g outdated
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/jo
https://github.com/isaacs/npm/issues/1428
On Jun 14, 2012, at 10:38, Graeme Foster wrote:
> I just noticed that when I ran npm outdated it said everything was hunky-dory
> but in fact some of my packages were out of date. The packages were
> up-to-date with respect to the versions specified in
That :)
Thanks, and looking forward to it.
On Friday, June 15, 2012, Ryan Schmidt wrote:
> https://github.com/isaacs/npm/issues/1428
>
--
--
Graeme Foster
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You recei
Me too. Is there anything else we should be doing to get that pull request
accepted? It feels like it's been forgotten.
On Jun 15, 2012, at 01:28, Graeme Foster wrote:
> That :)
>
> Thanks, and looking forward to it.
>
> On Friday, June 15, 2012, Ryan Schmidt wrote:
>> https://github.com/isaac
