Hi Fabrice, can you open a feature request for this? It's a ticket, and we can more easily track/prioritize it on our end this way. We generally avoid just adding "pagination and order by" in data lists because it usually means you're having to click through page after page and play around with order to find what you're looking for. We'd like to make it much easier :) So to do that, we'd love to learn more about the use case, because we have a feature on our roadmap to give a lot more insight into "which project uses a component", and I think you're definitely on the right track by using those headers. So screenshots, etc., would be great (and having this tracked in that feature request is so much simpler for us to manage internally). We can update this post once we have more insight, and if anyone is curious we can just reply with more info here :)

The tracking issue for this is here: PG-1309

I'm not familiar with Zabbix, but there are two things you can do to check about the status of the components (Database, Web, Service): If the database (SQL Server) wasn't working, or there was a problem with the website configuration, then visiting / will yield a 500 or some other not available message. You can just query the ProGet service run state directly. You could parse the text on the /connectors page or use the native API to get a status of the connectors.

Hi, I have tested with npm and all is working now. Thanks very much. Regards Fabrice

Not really I'm afraid... "Pulling with dependencies" would require implementing every dependency resolution algorithm of every version of every client, including the non-deterministic dependency resolution used by the npm client, and then somehow letting you select the algorithm version and the additional contet required by the algorithm (such as .net framework target versinon).