- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 230
 
feat: use the regitry url of npm by default #656
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
npm might not be on the path, we can't assume it's going to work this way. Also, it would introduce quite a heavy perf penalty to any corepack command, even those which have nothing to do with npm or its registry.
| 
           I will look into it in these few days.  | 
    
635b244    to
    9538922      
    Compare
  
    9ac82c2    to
    e3bbdea      
    Compare
  
    e3bbdea    to
    d29d556      
    Compare
  
    COREPACK_NPM_REGISTRY defaults to the regitry of npm| 
           There are many thumb-ups in #540, which means many people like this feature. Can someone help this PR move forward?  | 
    
Closes #540
Closes #535