On Wed, Jun 19, 2013 at 4:49 AM, Tomas Hrcka <thrcka(a)redhat.com> wrote:
> Instead I'd prefer to just silence this warning when `npm -g`
is used
> on Fedora. (But not without `-g`; I think this warning is useful for
> modules under development.) Will that work for you?
Yes I think that will be ok. How do you want to do that? Carry fedora
specific npm patch or is there option in npm config to disable it?
So it turns out that upstream has already taken care of this for us.
The newest version of npm no longer issues this warning. It instead
issues a warning if the "readme" value is not present in package.json,
which means it will only appear if there is a genuine upstream issue.
I'll be updating the npm stack really soon now (just waiting on a
couple more reviews [1]) so this problem will solve itself soon
enough. ;-)
-T.C.
[1]
https://bugzilla.redhat.com/showdependencytree.cgi?id=968919&hide_res...