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

Suggestion, npmrc as install - as a part of the guide for registry targeting #89

Open
Juksefantomet opened this issue Sep 28, 2022 · 0 comments

Comments

@Juksefantomet
Copy link

In relation with multiple registry configs for .npmrc and gemfury I have experienced multiple challenges.

Looking through various guides there are many suggestions but also challenges with these.

I see one item missing from your guide in relation with registry config, as one can now install npmrc through npm, the following procedure is available:

npm install npmrc -g
npmrc

First run initializes ~/.npmrcs folder

Within the folder the ~/.npmrcs/default will be initialized and populated by your ~/.npmrc if that file exists, and/or replace that file with a default config.

adding more profile files to ~/.npmrcs folder will allow you to use:

juksefantomet@juksefantomet:~$ npmrc
Available npmrcs:

   default
   profile_juan
 * profile_two

additionally it allows you to use:

juksefantomet@juksefantomet:~$ npmrc profile_juan
Removing old .npmrc (profile_two)
Activating .npmrc "profile_juan"

This allows for a good structure where multiple configs can cause issues if not scoped and guide wise allows from a more visible assistance to the end-user.

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

1 participant