Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

npm is ignoring loglevel setting in .npmrc #4186

Closed
ghost opened this Issue · 34 comments

8 participants

@ghost

No matter what I set loglevel to, it completely ignores it. My version of npm is 1.3.15.

@Zearin

:+1: Confirmed.

$ npm -v
1.3.15

$ node --version
v0.10.22
@luk-

Can not duplicate. What is the output of npm config ls. What does your .npmrc look like?

@ghost

npm config ls output:

    ; cli configs
    registry = "https://registry.npmjs.org/"

    ; userconfig /Users/bob/.npmrc
    loglevel = "warn"

    ; globalconfig /usr/local/etc/npmrc
    loglevel = "warn"

    ; node bin location = /usr/local/bin/node
    ; cwd = /Users/bob
    ; HOME = /Users/bob
    ; 'npm config ls -l' to show all defaults.

npm config ls --global output:

    ; cli configs
    global = true
    registry = "https://registry.npmjs.org/"

    ; userconfig /Users/bob/.npmrc
    loglevel = "warn"

    ; globalconfig /usr/local/etc/npmrc
    loglevel = "warn"

    ; node bin location = /usr/local/bin/node
    ; cwd = /Users/bob
    ; HOME = /Users/bob
    ; 'npm config ls -l' to show all defaults.

Yet when I run sudo npm update -g I get:

http://pastebin.com/hAKmhprJ

@Zearin

Here’s my own config output (from npm --global config ls -l):

; cli configs
global = true
long = true
registry = "https://registry.npmjs.org/"

; globalconfig /usr/local/etc/npmrc
browser = "open"
cache = "/Users/«username»/Library/Caches/npm"
https_proxy = 0
init-module = "/Users/«username»/.config/npm/npm-init.js"
loglevel = "warn"
userconfig = "/Users/«username»/.config/npm/.npmrc"
userignorefile = "/Users/«username»/.config/npm/.npmignore"
version = true

; default values
always-auth = false
bin-links = true
; browser = null (overridden)
; cache = "/Users/«username»/.npm" (overridden)
cache-lock-retries = 10
cache-lock-stale = 60000
cache-lock-wait = 10000
cache-max = null
cache-min = 10
color = true
coverage = false
depth = null
description = true
dev = false
editor = "mate --wait "
engine-strict = false
fetch-retries = 2
fetch-retry-factor = 10
fetch-retry-maxtimeout = 60000
fetch-retry-mintimeout = 10000
force = false
git = "git"
; global = false (overridden)
globalconfig = "/usr/local/etc/npmrc"
globalignorefile = "/usr/local/etc/npmignore"
group = 20
heading = "npm"
https-proxy = "http://localhost:8228"
ignore = ""
; init-module = "/Users/«username»/.npm-init.js" (overridden)
init.author.email = ""
init.author.name = ""
init.author.url = ""
init.version = "0.0.0"
json = false
link = false
local-address = undefined
; loglevel = "http" (overridden)
; long = false (overridden)
message = "%s"
node-version = "v0.10.22"
npat = false
npaturl = "http://npat.npmjs.org/"
onload-script = false
optional = true
parseable = false
pre = false
prefix = "/usr/local"
production = false
proprietary-attribs = true
proxy = "http://localhost:8228"
rebuild-bundle = true
registry = "https://registry.npmjs.org/"
rollback = true
save = false
save-bundle = false
save-dev = false
save-optional = false
searchexclude = null
searchopts = ""
searchsort = "name"
shell = "/usr/local/bin/bash"
shrinkwrap = true
sign-git-tag = false
strict-ssl = true
tag = "latest"
tmp = "/var/folders/dv/gckkgl896154qhgldh0v9t2c0000gr/T/"
umask = 18
unicode = true
unsafe-perm = true
usage = false
user = "nobody"
user-agent = "node/v0.10.22 darwin x64"
; userconfig = "/Users/«username»/.npmrc" (overridden)
; userignorefile = "/Users/«username»/.npmignore" (overridden)
username = ""
; version = false (overridden)
versions = false
viewer = "man"
yes = null

Operating System is OS X.

Node.js installed view brew install node --without-npm.

npm originally installed oldschool-style, via curl https://npmjs.org/install.sh | sudo bash.

@Zearin

P.S.: @CaptSaltyJack , you can edit your npm config output like so:

  • Edit your post on GitHub
  • Add this line before your config: ```ini
  • Add this line after your config: ```

Voila! Syntax-highlighted config, which will hopefully help this bug get squashed a little easier for @isaacs and fellow npm maintainers.

(Or not. :) Just trying to spread the syntax-highlighted love around the GitHubz.)

@jhs67

This happened to me - it turns out I had two version of npmlog in my module tree (the second was in npm-registry-client) The second one wasn't being initialized but it was be referenced. Try npm list -g and see if it is in there twice.

@ghost

I do have two npmlogs installed. Same version (0.0.6). One is under npm-registry-client and the other is under npm I believe. What should I do?

@jhs67

I just manually removed the second.

cd <npm-install-dir>/npm/node_modules/npm-registry-client
npm rm npmlog

You may need some sudo's in there depending on how things are installed.

I'm not sure how the second copy got there, I never did anything more than "npm update -g".

@rex

I apologize for bumping this, but this is still an issue for me. I applied the fix that @jhs67 and @CaptSaltyJack suggested above, and it worked great for a few days, but now it's back to the hyper-verbose logging of yesteryear. Is there not a way to permanently fix this? This seems like a bug in the way or priority that the config is read.

@timoxley
Collaborator

Some related discussion at the bottom of #4035 & a possible patch I/someone needs to investigate further over on npm/npm-registry-client#36

Could also be fixed simply by ensuring the npmlog for npm-registry-client doesn't get included in the published bundle, so it could be as simple as adding node_modules/npm-registry-client/node_modules/npmlog to .npmignore

@OverZealous

This is still an issue for me, it's very annoying to have to manually fix it every time I update npm.

@ghost

This is fixed for me now! npm version 1.3.26. Running sudo npm update -g no longer shows all the http messages. I only get this kind of output:

file-utils@0.1.5 /usr/local/lib/node_modules/generator-webapp/node_modules/yeoman-generator/node_modules/file-utils
├── rimraf@2.2.6
├── isbinaryfile@0.1.9
├── minimatch@0.2.14 (sigmund@1.0.0, lru-cache@2.5.0)
├── glob@3.2.8 (inherits@2.0.1)
├── findup-sync@0.1.2 (glob@3.1.21, lodash@1.0.1)
├── iconv-lite@0.2.11
└── lodash@2.1.0
hawk@1.0.0 /usr/local/lib/node_modules/npm/node_modules/node-gyp/node_modules/request/node_modules/hawk
├── cryptiles@0.2.2
├── sntp@0.2.4
├── boom@0.4.2
└── hoek@0.9.1
handlebars@1.0.12 /usr/local/lib/node_modules/bower/node_modules/handlebars
├── optimist@0.3.7 (wordwrap@0.0.2)
└── uglify-js@2.3.6 (source-map@0.1.31, async@0.2.10)
@OverZealous

I'm still seeing it under 1.3.26, but only after I did an npm update -g. I'd try it again, CapSaltyJack, just to be sure.

@ghost

Yep, ran sudo npm update -g again, and.. OH DAMN IT, man, you jinxed me! ;) It WAS working on my very last update. They maybe re-broke it?

@OverZealous

No, it simply re-added the npmlog package back in to npm-registry-client when you did the global update.

@ghost

But I never removed the npmlog package though.

@rex
rex commented

I eventually just gave up and accepted it. That was my highly scientific solution. Has any contact been made with the owner of the repository? And did adding the module to git ignore work?

@ghost

Are any of you developers on this? It would be great to hear from one of them on this issue.

@rex
rex commented

I am not, I leave the development of npm in the hands of greater developers than myself :-P

That said, it would be nice to hear something. I'm honestly not sure if this is a bug or if there's a reason that this is expected behavior. @isaacs is a smart fucking guy and I've spent more than my fair share of time learning lessons about things when I was sure I was right.

@timoxley
Collaborator

If this PR is merged npm/npm-registry-client#36 and the dependency in npm updated, then the problem should go away.

@ghost

Ok, so next npm update will fix this? (again)

@timoxley
Collaborator

Depends if that PR is merged.

@ghost

Sorry, PR = ?

@timoxley
Collaborator

pull request

@ghost

npm v1.4.15. Still an issue. ~/.npmrc file contents:

loglevel = error
@fibric

npm v1.4.27 still ignores ~/.npmrc
loglevel = warn

@othiym23 othiym23 added the support label
@othiym23
Owner

I can't reproduce this with any recent (newer than 1.4.23) version of npm. If there's still a bug here, we're going to need more details to reproduce and then fix it.

@fibric

My setup OSX 10.10 DP8, node v0.10.32 and npm v1.4.27
Installed node and npm via homebrew brew install node

When I do run npm update -g then I see allot of http messages.
When I do run npm install package or npm install -g package then I do see http messages as well.

Only when I do run npm update -g -d warn then I finally see not millions (ironic) lines of http messages.

That also the case on my company laptop where Windows7 pro x64 is installed.
Installed node on company machine via nodejs.msi64 from nodejs.org

npm config ls

; cli configs
registry = "https://registry.npmjs.org/"
user-agent = "npm/1.4.27 node/v0.10.32 darwin x64"

; userconfig /Users/fibric/.npmrc
loglevel = "warn"

; node bin location = /usr/local/bin/node
; cwd = /Users/fibric
; HOME = /Users/fibric
; 'npm config ls -l' to show all defaults.

npm config ls --global

; cli configs
global = true
registry = "https://registry.npmjs.org/"
user-agent = "npm/1.4.27 node/v0.10.32 darwin x64"

; userconfig /Users/fibric/.npmrc
loglevel = "warn"

; node bin location = /usr/local/bin/node
; cwd = /Users/fibric
; HOME = /Users/fibric
; 'npm config ls -l' to show all defaults.

npm config ls -l --global

; cli configs
global = true
long = true
registry = "https://registry.npmjs.org/"
user-agent = "npm/1.4.27 node/v0.10.32 darwin x64"

; userconfig /Users/fibric/.npmrc
loglevel = "warn"

; default values
always-auth = false
bin-links = true
browser = null
ca = null
cache = "/Users/fibric/.npm"
cache-lock-retries = 10
cache-lock-stale = 60000
cache-lock-wait = 10000
cache-max = null
cache-min = 10
cafile = undefined
cert = null
color = true
depth = null
description = true
dev = false
editor = "vi"
email = ""
engine-strict = false
fetch-retries = 2
fetch-retry-factor = 10
fetch-retry-maxtimeout = 60000
fetch-retry-mintimeout = 10000
force = false
git = "git"
git-tag-version = true
; global = false (overridden)
globalconfig = "/usr/local/etc/npmrc"
globalignorefile = "/usr/local/etc/npmignore"
group = 20
heading = "npm"
https-proxy = null
ignore-scripts = false
init-module = "/Users/fibric/.npm-init.js"
init.author.email = ""
init.author.name = ""
init.author.url = ""
init.license = "ISC"
json = false
key = null
link = false
local-address = undefined
loglevel = "warn"
; long = false (overridden)
message = "%s"
node-version = "0.10.32"
npat = false
onload-script = null
optional = true
parseable = false
prefix = "/usr/local"
production = false
proprietary-attribs = true
proxy = null
rebuild-bundle = true
registry = "https://registry.npmjs.org/"
rollback = true
save = false
save-bundle = false
save-dev = false
save-exact = false
save-optional = false
save-prefix = "^"
searchexclude = null
searchopts = ""
searchsort = "name"
shell = "/usr/local/bin/zsh"
shrinkwrap = true
sign-git-tag = false
spin = true
strict-ssl = true
tag = "latest"
tmp = "/var/folders/qp/66fm85q142d3_b40btryzgq80000gn/T"
umask = 18
unicode = true
unsafe-perm = true
usage = false
user = "nobody"
; user-agent = "npm/{npm-version} node/{node-version} {platform} {arch}" (overridden)
userconfig = "/Users/fibric/.npmrc"
username = ""
version = false
versions = false
viewer = "man"
@othiym23
Owner

What does npm config ls -l return?

Have you tried running npm config del loglevel?

I believe that there are a bunch of you with this problem, but we're all kind of stuck until I can reproduce this, and so far I can't. :/

@fibric

looks equally to npm config ls -l --global
npm config ls -l

; cli configs
long = true
registry = "https://registry.npmjs.org/"
user-agent = "npm/1.4.27 node/v0.10.32 darwin x64"

; userconfig /Users/fibric/.npmrc
loglevel = "warn"

; default values
always-auth = false
bin-links = true
browser = null
ca = null
cache = "/Users/fibric/.npm"
cache-lock-retries = 10
cache-lock-stale = 60000
cache-lock-wait = 10000
cache-max = null
cache-min = 10
cafile = undefined
cert = null
color = true
depth = null
description = true
dev = false
editor = "vi"
email = ""
engine-strict = false
fetch-retries = 2
fetch-retry-factor = 10
fetch-retry-maxtimeout = 60000
fetch-retry-mintimeout = 10000
force = false
git = "git"
git-tag-version = true
global = false
globalconfig = "/usr/local/etc/npmrc"
globalignorefile = "/usr/local/etc/npmignore"
group = 20
heading = "npm"
https-proxy = null
ignore-scripts = false
init-module = "/Users/fibric/.npm-init.js"
init.author.email = ""
init.author.name = ""
init.author.url = ""
init.license = "ISC"
json = false
key = null
link = false
local-address = undefined
loglevel = "warn"
; long = false (overridden)
message = "%s"
node-version = "0.10.32"
npat = false
onload-script = null
optional = true
parseable = false
prefix = "/usr/local"
production = false
proprietary-attribs = true
proxy = null
rebuild-bundle = true
registry = "https://registry.npmjs.org/"
rollback = true
save = false
save-bundle = false
save-dev = false
save-exact = false
save-optional = false
save-prefix = "^"
searchexclude = null
searchopts = ""
searchsort = "name"
shell = "/usr/local/bin/zsh"
shrinkwrap = true
sign-git-tag = false
spin = true
strict-ssl = true
tag = "latest"
tmp = "/var/folders/qp/66fm85q142d3_b40btryzgq80000gn/T"
umask = 18
unicode = true
unsafe-perm = true
usage = false
user = 0
; user-agent = "npm/{npm-version} node/{node-version} {platform} {arch}" (overridden)
userconfig = "/Users/fibric/.npmrc"
username = ""
version = false
versions = false
viewer = "man"
@fibric

npm config del loglevel
npm update -g updated npm now to v2.0.0
and this is the output now

npm update -g
npm WARN unmet dependency /usr/local/lib/node_modules/jshint/node_modules/cli/node_modules/glob requires minimatch@'0.3' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/jshint/node_modules/minimatch,
npm WARN unmet dependency which is version 0.4.0
strip-json-comments@0.1.3 /usr/local/lib/node_modules/jshint/node_modules/strip-json-comments
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npm-registry-client requires retry@'0.6.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/retry,
npm WARN unmet dependency which is version 0.6.1
opener@1.3.0 /usr/local/lib/node_modules/npm/node_modules/opener
date-now@0.1.4 /usr/local/lib/node_modules/jshint/node_modules/console-browserify/node_modules/date-now
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npm-registry-client requires retry@'0.6.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/retry,
npm WARN unmet dependency which is version 0.6.1
archy@0.0.2 /usr/local/lib/node_modules/npm/node_modules/archy
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npm-registry-client requires retry@'0.6.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/retry,
npm WARN unmet dependency which is version 0.6.1
ini@1.2.1 /usr/local/lib/node_modules/npm/node_modules/ini
minimist@0.0.8 /usr/local/lib/node_modules/npm/node_modules/mkdirp/node_modules/minimist
once@1.3.1 /usr/local/lib/node_modules/npm/node_modules/read-installed/node_modules/readdir-scoped-modules/node_modules/once
└── wrappy@1.0.1
npm WARN unmet dependency /usr/local/lib/node_modules/jshint/node_modules/cli/node_modules/glob requires minimatch@'0.3' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/jshint/node_modules/minimatch,
npm WARN unmet dependency which is version 0.4.0
underscore@1.6.0 /usr/local/lib/node_modules/jshint/node_modules/underscore
minimist@0.0.10 /usr/local/lib/node_modules/coffeelint/node_modules/optimist/node_modules/minimist
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npm-registry-client requires retry@'0.6.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/retry,
npm WARN unmet dependency which is version 0.6.1
retry@0.6.1 /usr/local/lib/node_modules/npm/node_modules/retry
async@0.2.10 /usr/local/lib/node_modules/sails-generate-new-gulp/node_modules/async
entities@1.0.0 /usr/local/lib/node_modules/jshint/node_modules/htmlparser2/node_modules/entities
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npm-registry-client requires retry@'0.6.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/retry,
npm WARN unmet dependency which is version 0.6.1
inflight@1.0.2 /usr/local/lib/node_modules/npm/node_modules/inflight
├── once@1.3.1
└── wrappy@1.0.1
nopt@2.1.2 /usr/local/lib/node_modules/coffee-script-redux/node_modules/nopt
└── abbrev@1.0.5
strip-ansi@1.0.0 /usr/local/lib/node_modules/npm/node_modules/columnify/node_modules/strip-ansi
└── ansi-regex@0.2.1
dezalgo@1.0.1 /usr/local/lib/node_modules/npm/node_modules/async-some/node_modules/dezalgo
├── asap@1.0.0
└── wrappy@1.0.1
semver@4.0.0 /usr/local/lib/node_modules/npm/node_modules/npm-install-checks/node_modules/semver
minimatch@0.4.0 /usr/local/lib/node_modules/jshint/node_modules/minimatch
├── sigmund@1.0.0
└── lru-cache@2.5.0
dezalgo@1.0.1 /usr/local/lib/node_modules/npm/node_modules/read-installed/node_modules/readdir-scoped-modules/node_modules/dezalgo
├── asap@1.0.0
└── wrappy@1.0.1
resolve@0.6.3 /usr/local/lib/node_modules/coffeelint/node_modules/resolve
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npm-registry-client requires retry@'0.6.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/retry,
npm WARN unmet dependency which is version 0.6.1
once@1.3.1 /usr/local/lib/node_modules/npm/node_modules/once
└── wrappy@1.0.1
readable-stream@1.1.13 /usr/local/lib/node_modules/jshint/node_modules/htmlparser2/node_modules/readable-stream
├── isarray@0.0.1
├── inherits@2.0.1
├── string_decoder@0.10.31
└── core-util-is@1.0.1
source-map@0.1.11 /usr/local/lib/node_modules/coffee-script-redux/node_modules/source-map
└── amdefine@0.1.0
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npm-registry-client requires retry@'0.6.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/retry,
npm WARN unmet dependency which is version 0.6.1
sha@1.2.4 /usr/local/lib/node_modules/npm/node_modules/sha
├── graceful-fs@3.0.2
└── readable-stream@1.0.31 (isarray@0.0.1, inherits@2.0.1, string_decoder@0.10.31, core-util-is@1.0.1)
cscodegen@0.1.0 /usr/local/lib/node_modules/coffee-script-redux/node_modules/cscodegen
glob@3.2.11 /usr/local/lib/node_modules/jshint/node_modules/cli/node_modules/glob
├── inherits@2.0.1
└── minimatch@0.3.0 (sigmund@1.0.0, lru-cache@2.5.0)
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/npm-registry-client requires retry@'0.6.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/retry,
npm WARN unmet dependency which is version 0.6.1
semver@4.0.0 /usr/local/lib/node_modules/npm/node_modules/semver
coffee-script@1.7.1 /usr/local/lib/node_modules/coffeelint/node_modules/coffee-script
└── mkdirp@0.3.5
fs-extra@0.10.0 /usr/local/lib/node_modules/sails-generate-new-gulp/node_modules/fs-extra
├── jsonfile@1.2.0
├── rimraf@2.2.8
├── ncp@0.5.1
└── mkdirp@0.5.0 (minimist@0.0.8)
semver@4.0.0 /usr/local/lib/node_modules/npm/node_modules/read-installed/node_modules/semver
npmconf@2.0.9 /usr/local/lib/node_modules/npm/node_modules/npmconf
├── uid-number@0.0.5
├── osenv@0.1.0
├── ini@1.3.0
├── once@1.3.1 (wrappy@1.0.1)
├── inherits@2.0.1
├── nopt@3.0.1 (abbrev@1.0.5)
├── mkdirp@0.5.0 (minimist@0.0.8)
├── semver@3.0.1
└── config-chain@1.1.8 (proto-list@1.2.3)
semver@4.0.0 /usr/local/lib/node_modules/npm/node_modules/normalize-package-data/node_modules/semver
glob@4.0.6 /usr/local/lib/node_modules/npm/node_modules/node-gyp/node_modules/glob
├── inherits@2.0.1
├── graceful-fs@3.0.2
├── once@1.3.1 (wrappy@1.0.1)
└── minimatch@1.0.0 (sigmund@1.0.0, lru-cache@2.5.0)
semver@4.0.0 /usr/local/lib/node_modules/npm/node_modules/npm-package-arg/node_modules/semver
escodegen@0.0.28 /usr/local/lib/node_modules/coffee-script-redux/node_modules/escodegen
├── estraverse@1.3.2
├── source-map@0.1.39 (amdefine@0.1.0)
└── esprima@1.0.4
semver@4.0.0 /usr/local/lib/node_modules/npm/node_modules/node-gyp/node_modules/semver
request@2.42.0 /usr/local/lib/node_modules/npm/node_modules/request
├── caseless@0.6.0
├── json-stringify-safe@5.0.0
├── aws-sign2@0.5.0
├── forever-agent@0.5.2
├── stringstream@0.0.4
├── oauth-sign@0.4.0
├── tunnel-agent@0.4.0
├── node-uuid@1.4.1
├── qs@1.2.2
├── mime-types@1.0.2
├── bl@0.9.3 (readable-stream@1.0.31)
├── form-data@0.1.4 (mime@1.2.11, async@0.9.0, combined-stream@0.0.5)
├── tough-cookie@0.12.1 (punycode@1.3.1)
├── http-signature@0.10.0 (assert-plus@0.1.2, asn1@0.1.11, ctype@0.5.2)
└── hawk@1.1.1 (cryptiles@0.2.2, sntp@0.2.4, boom@0.4.2, hoek@0.9.1)
init-package-json@1.0.1 /usr/local/lib/node_modules/npm/node_modules/init-package-json
├── promzard@0.2.2
├── read@1.0.5 (mute-stream@0.0.4)
├── semver@3.0.1
├── read-package-json@1.2.7 (github-url-from-username-repo@1.0.2, github-url-from-git@1.4.0, graceful-fs@3.0.2, lru-cache@2.5.0, normalize-package-data@1.0.2)
└── glob@4.0.6 (inherits@2.0.1, graceful-fs@3.0.2, once@1.3.1, minimatch@1.0.0)
npm-registry-client@3.2.2 /usr/local/lib/node_modules/npm/node_modules/npm-registry-client
├── npm-cache-filename@1.0.1
├── chownr@0.0.1
├── slide@1.1.6
├── graceful-fs@3.0.2
├── rimraf@2.2.8
├── retry@0.6.0
├── once@1.3.1 (wrappy@1.0.1)
├── npmlog@0.1.1 (ansi@0.3.0)
├── mkdirp@0.5.0 (minimist@0.0.8)
├── normalize-package-data@1.0.2 (github-url-from-username-repo@1.0.2, github-url-from-git@1.4.0)
├── semver@3.0.1
└── request@2.44.0 (caseless@0.6.0, json-stringify-safe@5.0.0, forever-agent@0.5.2, aws-sign2@0.5.0, stringstream@0.0.4, oauth-sign@0.4.0, tunnel-agent@0.4.0, node-uuid@1.4.1, qs@1.2.2, mime-types@1.0.2, bl@0.9.3, form-data@0.1.4, tough-cookie@0.12.1, http-signature@0.10.0, hawk@1.1.1)
esmangle@0.0.17 /usr/local/lib/node_modules/coffee-script-redux/node_modules/esmangle
├── estraverse@1.3.2
├── escope@1.0.1
├── esshorten@0.0.2 (estraverse@1.2.0)
├── escodegen@0.0.28
├── optimist@0.6.1 (wordwrap@0.0.2, minimist@0.0.10)
├── source-map@0.1.39 (amdefine@0.1.0)
└── esprima@1.0.4
request@2.44.0 /usr/local/lib/node_modules/npm/node_modules/node-gyp/node_modules/request
├── caseless@0.6.0
├── json-stringify-safe@5.0.0
├── aws-sign2@0.5.0
├── forever-agent@0.5.2
├── stringstream@0.0.4
├── oauth-sign@0.4.0
├── tunnel-agent@0.4.0
├── node-uuid@1.4.1
├── qs@1.2.2
├── mime-types@1.0.2
├── form-data@0.1.4 (async@0.9.0, mime@1.2.11, combined-stream@0.0.5)
├── bl@0.9.3 (readable-stream@1.0.31)
├── tough-cookie@0.12.1 (punycode@1.3.1)
├── http-signature@0.10.0 (assert-plus@0.1.2, asn1@0.1.11, ctype@0.5.2)
└── hawk@1.1.1 (cryptiles@0.2.2, sntp@0.2.4, boom@0.4.2, hoek@0.9.1)
glob@4.0.6 /usr/local/lib/node_modules/npm/node_modules/read-package-json/node_modules/glob
├── inherits@2.0.1
├── graceful-fs@3.0.2
├── once@1.3.1 (wrappy@1.0.1)
└── minimatch@1.0.0 (sigmund@1.0.0, lru-cache@2.5.0)
glob@4.0.6 /usr/local/lib/node_modules/npm/node_modules/glob
├── inherits@2.0.1
├── graceful-fs@3.0.2
├── once@1.3.1 (wrappy@1.0.1)
└── minimatch@1.0.0 (sigmund@1.0.0, lru-cache@2.5.0)

so no http but still much more output than npm update -g -d warn

@fibric

npm update -g -d warn

npm info it worked if it ends with ok
npm info using npm@2.0.0
npm info using node@v0.10.32
npm info outdated updating []
npm info ok
@fibric

after npm config del loglevel
npm config ls -l

; cli configs
long = true
registry = "https://registry.npmjs.org/"
user-agent = "npm/2.0.0 node/v0.10.32 darwin x64"

; default values
always-auth = false
bin-links = true
browser = null
ca = null
cache = "/Users/fibric/.npm"
cache-lock-retries = 10
cache-lock-stale = 60000
cache-lock-wait = 10000
cache-max = null
cache-min = 10
cafile = undefined
cert = null
color = true
depth = null
description = true
dev = false
editor = "vi"
engine-strict = false
fetch-retries = 2
fetch-retry-factor = 10
fetch-retry-maxtimeout = 60000
fetch-retry-mintimeout = 10000
force = false
git = "git"
git-tag-version = true
global = false
globalconfig = "/usr/local/etc/npmrc"
globalignorefile = "/usr/local/etc/npmignore"
group = 20
heading = "npm"
https-proxy = null
ignore-scripts = false
init-module = "/Users/fibric/.npm-init.js"
init.author.email = ""
init.author.name = ""
init.author.url = ""
init.license = "ISC"
init.version = "1.0.0"
json = false
key = null
link = false
local-address = undefined
loglevel = "warn"
; long = false (overridden)
message = "%s"
node-version = "0.10.32"
npat = false
onload-script = null
optional = true
parseable = false
prefix = "/usr/local"
production = false
proprietary-attribs = true
proxy = null
rebuild-bundle = true
registry = "https://registry.npmjs.org/"
rollback = true
save = false
save-bundle = false
save-dev = false
save-exact = false
save-optional = false
save-prefix = "^"
scope = ""
searchexclude = null
searchopts = ""
searchsort = "name"
shell = "/usr/local/bin/zsh"
shrinkwrap = true
sign-git-tag = false
spin = true
strict-ssl = true
tag = "latest"
tmp = "/var/folders/qp/66fm85q142d3_b40btryzgq80000gn/T"
umask = 18
unicode = true
unsafe-perm = true
usage = false
user = 0
; user-agent = "npm/{npm-version} node/{node-version} {platform} {arch}" (overridden)
userconfig = "/Users/fibric/.npmrc"
version = false
versions = false
viewer = "man"
@othiym23
Owner

A few things:
1. running npm update -g is a bad idea until #6247 is resolved; use one of these scripts to upgrade all your global packages instead.
2. npm update -g -d warn is not doing what you think it's doing. -d is not an alias for --loglevel. That command is trying to update a global package named warn and silently exiting because it's not found in your global modules. If you run npm update -g -d you should see much more output.
3. That's the correct and expected output for npm update -g when loglevel is set to "warn".

I believe that this issue has been resolved at some point in the last year, and am going to close it now. If you have specific problems with loglevel not being respected, open a new issue with the following:

  1. The output of npm c ls -l, preferably stashed in a gist.
  2. Your version of Node.
  3. Your OS (and whether you're using cmd.exe, the Node shell, or MSYS bash if you're running Windows).
  4. Your version of npm, which should be >= 2.0.0.
@othiym23 othiym23 closed this
@othiym23 othiym23 locked and limited conversation to collaborators
@othiym23 othiym23 removed the repro-please label
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Something went wrong with that request. Please try again.