Squash 'npm WARN prefer global' message if package is required as dep #1648

Closed
Marak opened this Issue Nov 3, 2011 · 11 comments

Comments

Projects
None yet

Marak commented Nov 3, 2011

Is it possible / easy to do / sane to not show the following WARN message if the package is required as a dependency?

 npm WARN prefer global npm@1.0.103 should be installed with -g

Since in this case, we are requiring npm programmatically in jitsu and as a dep in our package.json.

This isn't a high priority for us, but I wanted to ask. Thanks!

Owner

isaacs commented Nov 3, 2011

Yes, that would be good.

On Wed, Nov 2, 2011 at 21:52, Marak Squires
reply@reply.github.com
wrote:

Is it possible / easy to do / sane to not show the following WARN message if the package is required as a dependency?

    npm WARN prefer global npm@1.0.103 should be installed with -g

Since in this case, we are requiring npm programmatically in jitsu and as a dep in our package.json.

This isn't a high priority for us, but I wanted to ask. Thanks!

Reply to this email directly or view it on GitHub:
isaacs#1648

Contributor

arikon commented Sep 25, 2012

+1 on this

veged commented Sep 25, 2012

+1

Contributor

zxqfox commented Sep 26, 2012

+1

Contributor

ralt commented Mar 13, 2013

Could this issue be correctly tagged if it's still a valid feature request?

Owner

isaacs commented Mar 13, 2013

It's tagged as "nice to have" and "patch welcome".

+1

jgonera commented Apr 23, 2013

+1

Member

robertkowalski commented May 20, 2013

merged in 7bd570a i think

domenic closed this May 20, 2013

@saper saper added a commit to saper/npm that referenced this issue Jul 6, 2015

@saper saper Don't warn on prefer global for devDependencies
Windows Powershell assumes the command has failed
whenever something is written to stderr.

Followup-To: #1648
Fixes: #8517
ef3dd99

@saper saper added a commit to saper/npm that referenced this issue Jul 6, 2015

@saper saper Don't warn on prefer global for devDependencies
Windows Powershell assumes the command has failed
whenever something is written to stderr.

Followup-To: npm#1648
Fixes: npm#8517
bc5e97e

@saper saper added a commit to saper/npm that referenced this issue Jul 7, 2015

@saper saper Don't warn on prefer global for devDependencies
Windows Powershell assumes the command has failed
whenever something is written to stderr.

Followup-To: npm#1648
Fixes: npm#8517
cd9706c

@zkat zkat added a commit that referenced this issue Aug 26, 2015

@saper @zkat saper + zkat install: don't warn on preferGlobal for devDeps
Windows Powershell assumes the command has failed
whenever something is written to stderr.

Followup-To: #1648
Fixes: #8517
e960382

@zkat zkat added a commit that referenced this issue Aug 26, 2015

@saper @zkat saper + zkat install: don't warn on preferGlobal for devDeps
Followup-To: #1648
Fixes: #8517
PR-URL: #9409
PR-URL: #8841
bbb25f3

@othiym23 othiym23 added a commit that referenced this issue Aug 28, 2015

@saper @othiym23 saper + othiym23 install: don't warn on preferGlobal for devDeps
Followup-To: #1648
Fixes: #8517
PR-URL: #9409
PR-URL: #8841
1c90cbb

CKarper commented Sep 21, 2015

This is definitely back for me with v3.3.3, on Win64.

Reopening the issue at the request of users that are experiencing this behavior on v3.3.3.

ehsalazar reopened this Sep 21, 2015

Contributor

othiym23 commented Sep 21, 2015

Reclosing this in favor of #8517, because this issue is positively antique.

othiym23 closed this Sep 21, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment