Skip to content
Discussion options

You must be logged in to vote

Glad you figured it out.

My recommendation is always scope your packages, also you can create a private scope at the config file so the selected scope never goes to upstream and you will never have conflicts.

By default is the package manager the one that does the job and registry only follow the restrictions you define at the config file. By nature the package manager relies on what you set on the name at the package json file and not designed you warn you.

I hope help those advices.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@juanpicado
Comment options

Answer selected by mbtools
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants