-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add support for a different default registry and for scoped registries #17
Comments
Sure, yeah, makes sense - I don't have anything like this to test it on, so I'm afraid this one is on you 👍 |
sebinsua
pushed a commit
to sebinsua/danger-plugin-yarn
that referenced
this issue
Dec 5, 2018
sebinsua
pushed a commit
to sebinsua/danger-plugin-yarn
that referenced
this issue
Dec 5, 2018
sebinsua
added a commit
to sebinsua/danger-plugin-yarn
that referenced
this issue
Dec 6, 2018
sebinsua
added a commit
to sebinsua/danger-plugin-yarn
that referenced
this issue
Dec 6, 2018
sebinsua
added a commit
to sebinsua/danger-plugin-yarn
that referenced
this issue
Dec 6, 2018
sebinsua
added a commit
to sebinsua/danger-plugin-yarn
that referenced
this issue
Dec 6, 2018
…for different renders (orta#17)
sebinsua
added a commit
to sebinsua/danger-plugin-yarn
that referenced
this issue
Dec 6, 2018
…for different renders (orta#17)
sebinsua
added a commit
to sebinsua/danger-plugin-yarn
that referenced
this issue
Dec 7, 2018
…for different renders (orta#17)
sebinsua
added a commit
to sebinsua/danger-plugin-yarn
that referenced
this issue
Sep 6, 2019
…for different renders (orta#17)
For the test you could use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be good if this package had support for a different default registry and additional scoped registries.
This would help users in an 'Enterprise' setting. Especially if their private packages do not exist on
registry.npmjs.org
at all.The text was updated successfully, but these errors were encountered: