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!
Few @angular packages are not retrieved from api
-
Tested in both 4.0.6 and 4.0.11 version,
The following packages are the ones we’re attempting to consume:
"@angular/common": "^2.0.0-rc.1", "@angular/compiler": "^2.0.0-rc.1", "@angular/core": "^2.0.0-rc.1", "@angular/http": "^2.0.0-rc.1", "@angular/platform-browser": "^2.0.0-rc.1", "@angular/platform-browser-dynamic": "^2.0.0-rc.1", "@angular/router-deprecated": "^2.0.0-rc.1",All of them have the same issue which is that proget doesn’t like the @ in the name.
You can see the bug in action if you do an http request to the server:
I have given you the URLs which works with npmjs registry not with proget.
https://SERVERNAME/npm/DefaultNPM/@angular%2Fcommon
fails
error it throws "{"error":"ArgumentException","reason":"String is not a valid semantic version."}"https://SERVERNAME/npm/DefaultNPM/es6-promise
succeedsPerforming the same requests to the public npm server works correctly:
https://registry.npmjs.org/@angular%2Fcommon
succeedshttps://registry.npmjs.org/es6-promise
succeedsPlease let us know, if there is a fix available in any builds.
Product: ProGet
Version: 4.0.6 -
Also have this issue. DId you find a workaround?
-
Update to 4.1.3 has solved this issue for us.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login