Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
DevOps
-
We are trying to set up proget as a nuget and npm local store.
Nuget is up and running.
But we have a problem with the npm store.The feed has 2 connectors (the npm registry and our myGet feed):
- https://registry.npmjs.org
- https://<company>.myget.org/F/npmfeed/auth/<atuthid>/npm/
If we browse to a public package we get:
http://proget/npm/CompanyNpm/angular --> OK, we get the json
http://proget/npm/CompanyNpm/angular/-/angular-1.5.7.tgz --> OK, we get the tgz
This works fine.
If we browse to our local package webstack, we get:
http://proget/npm/CompanyNpm/webstack/ --> OK, we get the json
http://proget/npm/CompanyNpm/webstack/-/webstack-1.0.1.tgz --> fails with error 404Same issue when we do npm install webstack
Not sure if this is a proget of MyGet issue.
Thanks,
Erwin
Product: ProGet
Version: 4.1.1
-
It's hard to say where the issue lies, but I would suggest to attach ProGet to a proxy server like Fiddler, so you can watch the requests that are made to npm vs MyGet.
Ideally, a request to ProGet or MyGet should look and behave the same as a request to npmjs.org. But npm is an undocumented protocol, and there are a lot of quirks, so oftentimes it doesn't.