> A simple NuGet server implementation built on Node.js that provides essential NuGet v3 API endpoints
Why not build on .NET ?
oaiey 3 hours ago [-]
Simple question: why code it in nodejs if .net core is more than capable of running it?
kid64 1 hours ago [-]
Because that's how Claude decided to handle it.
Kwpolska 52 minutes ago [-]
Packaging tools for language/ecosystem X written in another language Y are always a red flag. They had to reinvent a bunch of wheels, such as parsing metadata, and they probably did it badly.
See also: uv.
loic-sharma 3 minutes ago [-]
FWIW, the NuGet package format and the v3 server protocol are fairly simple and well documented.
mandeepj 2 hours ago [-]
> Package importer: Included package importer from existing NuGet server
Any idea how much hard drive storage space would be needed?
loic-sharma 36 minutes ago [-]
If you import all packages on nuget.org? You’re likely looking at terabytes of data.
The import tooling can be used to migrate off another NuGet server implementation.
Why not build on .NET ?
See also: uv.
Any idea how much hard drive storage space would be needed?
The import tooling can be used to migrate off another NuGet server implementation.
Mine is 15 gig, but I imagine 90% of it is outdated versions.
edit: removed all but the latest version of each package, now it’s 3.3 GB. The biggest non-Microsoft package for me is documentformat.openxml…