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

Use of .npmrc config #16

Closed
IAfanasov opened this issue Nov 1, 2017 · 8 comments
Closed

Use of .npmrc config #16

IAfanasov opened this issue Nov 1, 2017 · 8 comments
Assignees

Comments

@IAfanasov
Copy link

Use .npmrc file to get the registry url

I have a private registry and then I run
install-peerdeps valhalla-engine-test

I get en error
ERR That package doesn't exist. Please try another.

That because global npm server is used instead of one that setup in .npmrc file

@nathanhleung
Copy link
Owner

Can you attach your personal .npmrc file so I can take a look at your config?

@IAfanasov
Copy link
Author

I'm not comfortable with public access to it. Sent you it in email to @gmail.com

@nathanhleung
Copy link
Owner

v1.4.0 adds a --registry option which allows you to specify a registry. Please try it out and let me know if you have any further issues.

@IAfanasov
Copy link
Author

Only 2 months passed and I'm again working on this task (:

It worked but took me time to figure out that https://npm.mydomain.com/ is not working and last slash should be removed. So the registry string should be https://npm.mydomain.com.

@nathanhleung
Copy link
Owner

Thanks - I added a note to the README about not including the trailing slash

@IAfanasov
Copy link
Author

IAfanasov commented Jan 3, 2018

@nathanhleung as a one of the ux rules says: better prevent user opportunity to make error rather then make good error message. so, it would be definitely better to make it work with and without trailing slash

@nathanhleung
Copy link
Owner

Actually, that's a good idea. I'll reopen this and put this on the feature roadmap. Thanks!

@nathanhleung nathanhleung reopened this Jan 3, 2018
@nathanhleung
Copy link
Owner

nathanhleung commented Jan 23, 2018

Fixed in a57d4f5 and published in v1.5.0. Thanks again for the idea.

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

No branches or pull requests

2 participants