dotnet6-openapi VS BaGet

.NET Web API has great tooling for generating OpenAPI on build. Once you have this, you can easily generate TypeScript bindings for your front-end. See also: https://github.com/CharlieDigital/dotnet6-openapi

This will scaffold a project which is more or less the exact same as Flask, Express, or any other "easy" framework.

OpenAPI output is built-in, but tooling for development does require a bit of knowledge (agree that Microsoft would benefit from making this work out of the box).

A small repo here showing how to connect OpenAPI and front-end TypeScript client generation: https://github.com/CharlieDigital/dotnet6-openapi

I have one example that shows how to do this with Vue and Svelte: https://github.com/CharlieDigital/dotnet6-openapi

A lot of the work I've done is closed source, but I do have a simple template here that is a typical starting point: https://github.com/CharlieDigital/dotnet6-openapi

As others have mentioned, you want NuGet. However, beyond the directory approach that was already mentioned, people may be interested to know that you can also do a web hosted version or if you prefer you can use the full NuGet Gallery project that powers nuget.org. At this point there's like 20 different ways to do it now. Hanselman had a list of some options a while back. BaGet is kind of interesting on that list.

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

You could try self hosting a baget instance, it supports read through caching too (probably all the custom nuget servers do) https://github.com/loic-sharma/BaGet

I was able to get Baget installed and configured as an Azure Container Instance.

NuGet server - BaGet (https://github.com/loic-sharma/BaGet)

I created another CI, for Baget, which also uses sqlite. It has a similar problem with file locking: