-
Notifications
You must be signed in to change notification settings - Fork 31k
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
[json] Autodetect npm registry in package.json dependencies autocomplete #7430
Comments
Actually it could follow
I think the job here is to seek these paths inside |
As you saw, it's currently not possible to configure the registry we use. I'm afraid this is not on the top of the backlog, help is welcome... |
Well, this is really nice to have feature for our team, so I tried to figure it out. As @aeschli wrote above, the problem is the As you can find in the official documentation:
The offical public registry does not support And the problem is that the mentioned path is not basically supported in any other registry (eg. VSTS registry). And I am affraid there is no cross-registry-working solution. It is piece of cake to download at least semver info, but intellisense for package names is not so easy. So only thing to do is to find out how to search package names in registry. Any ideas? Edit: I found on stackoverflow this solution. It is possible to use:
so |
To keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed. |
First of all, congratulations for such a nice integration in package.json, with Schema Store support and server packages autocomplete.
I noted here that NPM's default registry is hardcoded, even if a custom registry was set by
npm config set registry
.Is there any possible way to use a registry provided by the user instead of the default one? Does JavaScript extension even provide any extensibility or customization at this point?
The text was updated successfully, but these errors were encountered: