Registry Protocol Support · Issue #340 · npm/statusboard · GitHub
//voltron/issues_fragments/issue_layout" data-turbo-transient="true" />
Skip to content
Type / to search
Sign in<br>Sign upAppearance settings
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
Uh oh!
There was an error while loading. Please reload this page.
npm
statusboard
Public
Notifications<br>You must be signed in to change notification settings
Fork<br>72
Star<br>204
Registry Protocol Support #340
New issue<br>Copy link
New issue<br>Copy link
Open
Open<br>Registry Protocol Support#340
Copy link
Description
darcyclarke<br>opened on Apr 14, 2021
Issue body actions
Problem statement
Users want the ability to easily configure specific packages to be downloaded from specific registries.
Features
a user is able to define & install dependencies with a prefixed registry: protocol spec; Configuring which registry the tarball is fetched from (ex. registry:#specifier)
Exit criteria
RFC doc outlining implementation is written & accepted
feature-set is fully implemented/functioning
tests are written for coverage of this feature-set
documentation has been updated for install (ie. specifically for package specs)
documentation has been updated for package.json (ie. specifically for package specs)
Useful Links
RRFC
Reactions are currently unavailable
Metadata<br>Metadata<br>Assignees
No one assigned
Labels
No labelsNo labels
Type
No type
Projects
No projects
Milestone
No milestone
Relationships
None yet
Development
No branches or pull requests
Issue actions<br>Open in GitHub Copilot app
You can’t perform that action at this time.