Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> that the official repo can only "unlist" packages, not delete them or that the publish times sometimes have horrible delays

It's to avoid the npm left-pad problem. nuget.org packages are idempotent.

For the publish times, I found out you can cut it in more than half if you tell nuget to ignore caches.



I know... but sometimes it is a bad thing for indie hackers testing around :-)

Draft releases would be awesome.


You don't have to use Nuget.org, it's just the public community version of a Nuget package repo.

You can use your own private repos like MyGet[1] or Github Packages [2].

1. https://www.myget.org/ 2. https://docs.github.com/en/packages/working-with-a-github-pa...


Yeah I know all this, you can even use BaGet[1] symbol server to cache or manage private dependencies in an enterprise network. That is not the point... I think that the most used tool / platform should provide more flexibility for non-enterprise or less expierienced developers.

No offense, I like nuget, but I recently made a typo and checked in 0.0.23 instead of 0.0.2. Now, everytime I add a dependency that is < 0.0.23 to a project, that has not been synchronized / validated yet (the other problem I described), it automatically takes the best match, which is 0.0.23 assuming to be the newest package, even if unlisted.

I also burned a 1.0.0 because of a failing script like that... not really bad, but annoying...

https://github.com/loic-sharma/BaGet


FYI Nuget also work with folders.

Drop nupkg in a folder, use it as a source, you now have a "feed".


Why not just setup a local feed?


Idempotent, in which way? Do you perhaps mean immutable?


Yes, sorry, I meant immutable, not idempotent.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: