{"action":"created","issue":{"url":"https://api.github.com/repos/jspm/jspm-cli/issues/1164","labels_url":"https://api.github.com/repos/jspm/jspm-cli/issues/1164/labels{/name}","comments_url":"https://api.github.com/repos/jspm/jspm-cli/issues/1164/comments","events_url":"https://api.github.com/repos/jspm/jspm-cli/issues/1164/events","html_url":"https://github.com/jspm/jspm-cli/issues/1164","id":108294225,"number":1164,"title":"npm Enterprise and scoped packages","user":{"login":"gustavnikolaj","id":1371503,"avatar_url":"https://avatars.githubusercontent.com/u/1371503?v=3","gravatar_id":"","url":"https://api.github.com/users/gustavnikolaj","html_url":"https://github.com/gustavnikolaj","followers_url":"https://api.github.com/users/gustavnikolaj/followers","following_url":"https://api.github.com/users/gustavnikolaj/following{/other_user}","gists_url":"https://api.github.com/users/gustavnikolaj/gists{/gist_id}","starred_url":"https://api.github.com/users/gustavnikolaj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gustavnikolaj/subscriptions","organizations_url":"https://api.github.com/users/gustavnikolaj/orgs","repos_url":"https://api.github.com/users/gustavnikolaj/repos","events_url":"https://api.github.com/users/gustavnikolaj/events{/privacy}","received_events_url":"https://api.github.com/users/gustavnikolaj/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-09-25T09:41:11Z","updated_at":"2015-09-25T11:01:25Z","closed_at":null,"body":"I've looked through a number of issues, trying to see if this was already covered by someone else. But I haven't found any answers. #944 mentions scoped packages in general, and not private scoped packages. #899 mentions that they are supported from 0.16 - which I am using.\r\n\r\nWe have an npm Enterprise installation in house. That means that our scoped packages are not just using a normal scope that uses the original registry, but they are using a scope which should point to another registry.\r\n\r\nIn .npmrc it's handled by setting a value `@myScope:registry = \"http://foo.bar.com\"`.\r\n\r\n```\r\nproject $ jspm install foo=npm:@myScope/foo\r\n     Looking up npm:@myScope/foo\r\n\r\nerr  Repo npm:@myScope/foo not found!\r\n\r\nwarn Installation changes not saved.\r\n```\r\n\r\nIf I change the npm registry value in `~/.jspm/config` to my npme-registry it works as expected.\r\n\r\nAm I right, when I assume that this is not supported? Do you have any pointers towards where I should start if I were to submit this functionality as a PR?"},"comment":{"url":"https://api.github.com/repos/jspm/jspm-cli/issues/comments/143187590","html_url":"https://github.com/jspm/jspm-cli/issues/1164#issuecomment-143187590","issue_url":"https://api.github.com/repos/jspm/jspm-cli/issues/1164","id":143187590,"user":{"login":"gustavnikolaj","id":1371503,"avatar_url":"https://avatars.githubusercontent.com/u/1371503?v=3","gravatar_id":"","url":"https://api.github.com/users/gustavnikolaj","html_url":"https://github.com/gustavnikolaj","followers_url":"https://api.github.com/users/gustavnikolaj/followers","following_url":"https://api.github.com/users/gustavnikolaj/following{/other_user}","gists_url":"https://api.github.com/users/gustavnikolaj/gists{/gist_id}","starred_url":"https://api.github.com/users/gustavnikolaj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gustavnikolaj/subscriptions","organizations_url":"https://api.github.com/users/gustavnikolaj/orgs","repos_url":"https://api.github.com/users/gustavnikolaj/repos","events_url":"https://api.github.com/users/gustavnikolaj/events{/privacy}","received_events_url":"https://api.github.com/users/gustavnikolaj/received_events","type":"User","site_admin":false},"created_at":"2015-09-25T11:01:25Z","updated_at":"2015-09-25T11:01:25Z","body":"We could make the property registryUrl on the NpmLocation class into a function, which would return the registryUrl when given a package name, or even just a scope name. If no arguments is given, it will just return whatever it does now.\r\n\r\nhttps://github.com/jspm/npm/blob/master/lib/npm.js#L37\r\n\r\nIt's needed to support different registries depending on the scope, in order to support NPM Enterprise properly. Would this change go against any conventions or reasoning in the project, that I'm not aware of?"}}