Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RRFC] Registry per package on the same organisation #211

Closed
baloran opened this issue Aug 24, 2020 · 2 comments
Closed

[RRFC] Registry per package on the same organisation #211

baloran opened this issue Aug 24, 2020 · 2 comments
Assignees

Comments

@baloran
Copy link

baloran commented Aug 24, 2020

Motivation ("The Why")

We want to install some private package from github registry and some public package from npm registry with the same scope organisation.

Example

My .npmrc ⬇️

@unlikelystudio/simpleql:registry=https://registry.npmjs.org
@unlikelystudio:registry=https://npm.pkg.github.com/

How

Current Behaviour

The SimpleQL package try to be installed from github registry (eg: https://npm.pkg.github.com) instead of npm.

Desired Behaviour

SimpleQL Package use the npm registry and the others github registry.

I have searching arround some solution with git install repository directly but is not very great solution. Here to discuss of solution or pull request I can do.

@ruyadorno ruyadorno added the Agenda will be discussed at the Open RFC call label Aug 26, 2020
@darcyclarke darcyclarke added Question further information is requested Registry and removed Question further information is requested Registry labels Sep 2, 2020
@wesleytodd
Copy link

One new hazard this introduces: in older versions of npm which do not support this feature might result in users installing code from an unexpected registry and therefore opening the door to a RCE or otherwise getting the wrong code. By back porting the feature or atleast an error to npm@6 will help reduce the issue.

Also, will this support unscoped package names? I think it should.

@darcyclarke darcyclarke removed the Agenda will be discussed at the Open RFC call label Sep 18, 2020
@darcyclarke darcyclarke self-assigned this Sep 18, 2020
@ruyadorno
Copy link
Contributor

Let's follow up with the conversation in the actual RFC PR #217 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants