It is a big contribution to opensource it. The work behind the data is huge and extremely significant. Thanks Troy!
The service implementation that I did with a bit different technical requirement is here https://github.com/janos/compromised as an alternative. It is actively used behind the NewReleases.io service.
It focuses on extremely low memory usage and supporting very high request rates on a commodity hardware, cheap vps or cloud instances.
I must say that I also relate with the author and would add that making things just for fun or your own curiosity or even need, can be beneficial to others too, directly or indirectly. With every toy project, new skills are acquired. Useful or not, you cannot now at the time, but I can say that if I did not make toy projects, I would not have jobs that I had and some of the projects that others also find useful, like https://newreleases.io, would not exist.
Given the popularity of Alpine it is important to update images as soon as possible given how many significant updates are there. Services like [1] help a lot for that...
Tailwind released 2.0, but it is a result of constant work releasing new versions gradually and listening to the users. This is a very active project and it is good to keep an eye on new things https://newreleases.io/npm/tailwindcss. Actually, 2.0.1 is out already. :)
It is a manual update, replacing, for now. Automated update would be a good improvement, for sure. It is not there just as it is a recently started project. Also updates are not so frequent.
Or if you do not and you like official releases, you can use some of the services like https://newreleases.io to get notification and install using official installer.
And also very important to watch for changes of your dependencies, as they can be quite dynamic. A single review too early or too late in the development process may have misleading results. Watching for commit changes is too time consuming, so watching for releases is a bit easier, especially if you use something like https://newreleases.io or other similar sites.
This will be very neat just as GitHub user experience is so far. Centralization is a questionable, but it looks like that the community values much more the convenience than decentralization and privacy. In any case, it is excellent to have multiple choices beside other registries. I hope that other services like https://newreleases.io will catch up and support this registry as well. But, maybe this would even make them obsolete and everything a bit more centralized.
Thank you very much for Bleve! It was useful for me on a few projects. And, do not be afraid to break things in the future major version, modules are handling that nicely.
The service implementation that I did with a bit different technical requirement is here https://github.com/janos/compromised as an alternative. It is actively used behind the NewReleases.io service.
It focuses on extremely low memory usage and supporting very high request rates on a commodity hardware, cheap vps or cloud instances.