Publishing scoped packages

[hvaara]

When I try to publish a scoped package I get an error:

$ npm publish
npm ERR! publish Failed PUT 403
npm ERR! Darwin 16.4.0
npm ERR! argv "/usr/local/Cellar/node/7.4.0/bin/node" "/usr/local/bin/npm" "publish"
npm ERR! node v7.4.0
npm ERR! npm  v4.0.5
npm ERR! code E403

npm ERR! forbidden user: hvaara not authorized to modify @hvaara/tester
npm ERR! Added: _id
npm ERR! Added: name
npm ERR! Added: dist-tags
npm ERR! Added: versions
npm ERR! Added: readme
npm ERR! Added: maintainers
npm ERR! Added: time
npm ERR! Added: license
npm ERR! Added: readmeFilename
npm ERR! Added: _revisions
npm ERR! Added: _attachments
npm ERR! Added: users: @hvaara/tester
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/hvaara/dev/kickback/tester/npm-debug.log

The name field in package.json is set to @hvaara/tester, other than that everything is a minimal npm init.

I'm using the prebuilt docker containers with the docker-compose.yml from master.

Am I doing something wrong, or are scoped packages not supported? Publishing packages that are not scoped works fine.

[shaunwarman]

@hvaara unfortunately, we never got around to adding scope support. GET from public registry will work fine, but you're right.. attempting to publish to a private instance here will currently error.

[hvaara]

Thanks @shaunwarman, I may or may not end up working on this. If I do, do you want a PR upstream?

[shaunwarman]

Of course! That would be great.

[shaunwarman]

Hey @hvaara sorry I haven't had time to jump into this. Before I do, anything you were able to dig up or attempt?

[hvaara]

Hey @shaunwarman We ended up using the official npm registry. I did investigate how npm does it against registry.npmjs.org. Seems like the / in the package name is escaped into %2f. If we do that against couch it might work.

Have you already started working on this? Unless you need it right away internally I could commit to look at this if you'd like. Shouldn't be too much work.

[shaunwarman]

That would be great. I honestly haven't other than investigating the npm client changes.

[Paul-Todd]

Did anyone fix this? I've hit this issue too

[hvaara]

Unfortunately not. We ended up going with npm.