Feature/support alternative npm registries #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What:
Support different package scope then the @loupeteam by either using the
@yourscope/packname
prefix or supply an additional argument--scope=@yourscope
.Why:
Related to #8 and #37. Add support for other npm registries then the default loupeteam registry.
This make it possible to host your own package repo for LPM.
Usage
Add suport for other npm registries
Default the scope @loupeteam is added to each provide package name.
With this commit you can use also other or even mixed repositories to pull packages from.
Usage:
--scope=<yourscope>
to the LPM command.examples:
LPM commands not supported with other registries than the default @loupetam:
If login is required for other registries use the
npm
tools instead.