Aha! That's the ticket -- setting ErrorOutputLogLevel to "Warning" is just what I was looking for. For some reason I had thought the option would do the inverse (e.g. elevate warnings to errors). Thanks a ton for the help, -J

I get the same issue with v4.3.1 (Build 5). With nuget, I can search (via connector) to list all packages available on nuget.org. But with npm, unless I manually add packages via npm connector, the search shows a blank page.

When you download a package, then package is cached by default; if you download aggin, it will use your local cache instead of re-downloading from npm. The caching is transparent, so they will not show up as local packages.

Update to 4.1.3 has solved this issue for us.

We have been running the update since it has been out and it does look like it has fixed our issues with random failing npm restores. Running my LinqPad test script now (which makes 32 concurrent requests for the same resource), still makes it "fail", but now with a 404 as you described, instead of returning an empty package. (Which is still quite weird behavior IMO...) Thanks for the quick response and help on solving this!

You might be getting that message if you have Windows Integrated AUthentication enabled; this is unfortunately not supported in the npm client. Otherwise if you follow the steps in the npm tutorial it should work just fine.

Thanks! We will have this fixed in ProGet 4.0.14, which will be released within the hour.

You can install a separate website in IIS that points to the same home directory, which supports forms authentication, then use that separate URL for npm & bower. With a separate IIS site, upgrading won't touch it so it will upgrade as per normal with the installer.

Well, there is literally no js error since the browser loads forever and never returns. There is also no logs in the admin section.

Nevermind. It was due to my local cache in ~\AppData\Roaming\npm-cache so npm never tried to fetch them from the server. I cleaned it out and ran npm install and now everything works! Sorry for the noise.

It's hard to say... 3.6 was almost a year ago, and I know the npm api/format specification has likely changed since then. So, it could be a related to that...

Hi, the package is superagent-mocker 0.3.0 fetched from registry.npmjs.org: see display in the npmjs.org : display of superagent-mocker 0.3.0 in npmjs org see display in proget

Dismiss my recent answer It works fine At some point the connector was removed from the feed which explains why nothing got listed even though the connector was fine. I'm really sorry for this! Thanks for the support!

Are you sure the requests are actually leaving your desktop? Obviously The Real WTF here is doing ONE THOUSAND outbound network requests for a contiguous operation. Since they managed to write a client that does that, I think there's no chance that they can competently build a proper network request pool, let alone one that reports proper messages. The NuGet client had a problem with this a while ago, where it was doing similar nonsense that lead to race conditions that only appeared when you used ProGet b/c the requests were being served significantly faster than NuGet.org.

Do you mean from the ProGet UI? There is not currently such a feature.

Unless something has changed, you cannot use Integrated Authentication with npm because the client doesn't support it: http://inedo.com/support/questions/2647 However, if you enable LDAP authentication in ProGet and then disable Integrated Authentication, you'll be able to use your Windows credentials. If it's the backslash that isn't supported, try the Active Directory provider, which supports the user@domain syntax.

Thanks, Dan. It looks like this resolves the issue I was seeing as well! Now I just have to figure out why my ProGet server won't do a full index of npm without having the connection forcibly closed, but at least I'm back in business.

Is this feature now available? Where could I find documentation to this?

It's hard to say why there's a discrepancy, but you can just re-index the entire connector. Just run the "FullNpmConnectorIndex " scheduled task, accessible from the admin portal. This will take several minutes. There will be a LOT of warnings about "missing versions property". You can ignore thesethey are effectively invalid npm packages that they return anyway with the index request.

ProGet 4.0.11 is now available, which includes support for scoped packages. You can get it from the downloads page: http://inedo.com/proget/download