Skip to content


npm adduser: Error: conflict Document update conflict #4092

johnhunter opened this Issue · 3 comments

4 participants


Steps to reproduce

  • on a windows machine I have not published from
  • npm adduser with incorrect password
  • reset password on admin site
  • npm adduser with new password

Actual result

Error with the following response

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'adduser' ]
2 info using npm@1.3.11
3 info using node@v0.10.20
4 verbose node symlink C:\Program Files\nodejs\\node.exe
5 verbose adduser before first PUT { name: 'johnhunter',
5 verbose adduser   salt: 'XXXXX',
5 verbose adduser   password_sha: 'XXXXX',
5 verbose adduser   email: '<email>',
5 verbose adduser   _id: 'org.couchdb.user:johnhunter',
5 verbose adduser   type: 'user',
5 verbose adduser   roles: [],
5 verbose adduser   date: '2013-11-05T13:35:06.986Z' }
6 verbose url raw /-/user/org.couchdb.user:johnhunter
7 verbose url resolving [ '',
7 verbose url resolving   './-/user/org.couchdb.user:johnhunter' ]
8 verbose url resolved
9 info trying registry request attempt 1 at 13:35:06
10 http PUT
11 http 409
12 verbose adduser update existing user
13 verbose url raw /-/user/org.couchdb.user:johnhunter
14 verbose url resolving [ '',
14 verbose url resolving   './-/user/org.couchdb.user:johnhunter' ]
15 verbose url resolved
16 info trying registry request attempt 1 at 13:35:08
17 http GET
18 http 200
19 verbose adduser userobj { name: 'johnhunter',
19 verbose adduser   salt: 'XXXXX',
19 verbose adduser   password_sha: 'XXXXX',
19 verbose adduser   email: '<email>',
19 verbose adduser   _id: 'org.couchdb.user:johnhunter',
19 verbose adduser   type: 'user',
19 verbose adduser   roles: [],
19 verbose adduser   date: '2013-11-05T13:35:06.986Z' }
20 verbose url raw /-/user/org.couchdb.user:johnhunter/-rev/2-66d2703248590980b2fcd732e560af70
21 verbose url resolving [ '',
21 verbose url resolving   './-/user/org.couchdb.user:johnhunter/-rev/2-66d2703248590980b2fcd732e560af70' ]
22 verbose url resolved
23 info trying registry request attempt 1 at 13:35:09
24 http PUT
25 http 409
26 verbose adduser back [ [Error: conflict Document update conflict.: -/user/org.couchdb.user:johnhunter/-rev/2-66d2703248590980b2fcd732e560af70],
26 verbose adduser   { error: 'conflict', reason: 'Document update conflict.' },
26 verbose adduser   '{"error":"conflict","reason":"Document update conflict."}' ]
27 error Error: conflict Document update conflict.: -/user/org.couchdb.user:johnhunter/-rev/2-66d2703248590980b2fcd732e560af70
27 error     at RegClient.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-registry-client\lib\request.js:272:14)
27 error     at Request.self.callback (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:129:22)
27 error     at Request.EventEmitter.emit (events.js:98:17)
27 error     at Request.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:873:14)
27 error     at Request.EventEmitter.emit (events.js:117:20)
27 error     at IncomingMessage.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:824:12)
27 error     at IncomingMessage.EventEmitter.emit (events.js:117:20)
27 error     at _stream_readable.js:920:16
27 error     at process._tickCallback (node.js:415:13)

See also #2241


Is this issue now resolved?

I believe it is no longer possible to hit that code path (Document update conflict) and in order to change password or email address, a separate web form must be used -- it can't be done through npm anymore. Thus I think this error cannot be reproduced anymore.

We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and open a new issue!)



Closing as abandoned / resolved.

@othiym23 othiym23 closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.