Set custom registries instead of public registries #33735
Replies: 1 comment 2 replies
-
Fixed with the help from @notpeter |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm having an issue that I'm hoping someone can help me with.
I'm trying to use Zed in my work environment, but unfortunately, I cannot access public registries due to our security guidelines. I need to configure Zed to use our internal Artifactory instance, which acts as an npm proxy, but whatever I try seems to be ignored. Zed's npm is always trying to connect to the public registry.
The command fails with the following error, showing it's still trying to reach https://registry.npmjs.org/:
Here is a part of my configuration in Zed's settings.json:
I have also tried setting "strict-ssl": false, but this setting is also completely ignored. Additionally, I tried setting the standard npm environment variables, but they had no effect either:
Does anyone have an idea how I can get Zed to respect these npm configurations in my work environment?
Beta Was this translation helpful? Give feedback.
All reactions