2 ms·
Sure but what's the point of types if none of the packages you use are using it or are even tested in the first place? I also have the same story on the JS sid
by realusername 3y ago
Sure but what's the point of types if none of the packages you use are using it or are even tested in the first place?
I also have the same story on the JS side, we upgraded the package to open notifications, they broke the API and kept the types the same. Now we added a test that notifications are working (we're basically doing the package maintainer's job).
Ruby's update story isn't prefect, far from it but I'll take it any day against npm. I worry at every package upgrade on the JS side.
What's making it even worse is that the stdlib is very limited on the JS side, so this effect is compounded by the number of packages needed to fill the gap.