Support for custom shorthand URL prefix about normalize-package-data HOT 2 CLOSED

@ovmjm: How would you imagine this to work with npm itself, if at all?

I can imagine extending the exported normalize function with an options argument, making room for overriding some defaults, but unless you'd use this normalize function on its own, you won't have access to it. If you want npm to respect such an option, npm would need to support that explicitly, i.e. it would need to an extra configuration setting or command line argument.

The only way I see to sidestep npm in this regard would be to have this function look at some magic environment variable or so, which I don't feel good about.

I think it could make sense to have npm support an config setting for automatically expanding repo url shorthand for private packages, but this is in the hands of @isaacs .

@isaacs

1. What do you think of accepting arguments in the form of normalize(data, warnFn, options) ?
2. Are you willing to add support in npm for "expanding" private repo url short-hand differently than public packages?

from normalize-package-data.

I'd file an issue on isaacs/npm . If people agree it's a good thing, I'll add support for it, so npm can support it on the whole. Without explicit support from npm, I don't think adding support for it here is gonna be of much use to you.

I generally like the idea, although I think it could be better to allow differentiating between private and public packages for which "short-hand resolver" to use. As soon as npm reaches a public package, it can be assumed that all packages using short-hand will be available from GitHub. This would lighten the burden on the private git server. Bing able to override the resolver for public packages as well could be handy for either doing clever overrides for dependencies (not sure if that's a smart thing) or removing dependence on GitHub.

I don't think npm has any notion of "local" configuration currently (like Bower does with its local bowerrc files), so that would essentially entail a second feature request for npm, if needed.

from normalize-package-data.