Proget NPM package web UI gets slow with multiple version of packages

Hi,

We discovered an issue with Proget's NPM package web page that becomes inaccessible when multiple version of a package is uploaded. As soon as 10 to 15 version of the same package is uploaded to the feed, it's package page (not the feed page) becomes inaccessible (The web browser load indefinitely). The npm feed itself is still perfectly working and package can be downloaded correctly.

I've been able to reproduce this on 2 different IIS installation with version 4.0.8 and 4.0.9.

Thanks,
Carl

Product: ProGet
Version: 4.0.9

Are there any example packages you're aware of the exhibit this behavior?

There are a lot of public packages with lots more than 10-15 versions..

You are right, but it doesn't seems to affect public packages from connectors, only local ones.

I just tested with an empty package and uploaded 15 version of it using "npm version minor" to bump the version and "npm publish" to push it to the feed. The package page becomes inaccessible instantly.

Can you check to see what JavaScript errors are occurring? An error might also be logged in the Admin > Errors as well. It's likely, a data processing thing or something... hard to say.

You may want to submit these errors via a submit ticket, as that will be easier to attach files to.

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