[josephpmay]

I built a major project in Meteor last summer, and it was a big mistake. For the most part, Meteor itself is stable and being actively developed, but many of the packages are experiencing severe rot, and one of the developers of a few of the most used meteor packages recently went out of business and took all their documentation down with them.

[maxsavin]

Do you mean Meteor Toys? I'm working to get the site back up :) just been busy .. I'm actually contemplating an all-new version.

[aogaili]

The Meteor official guide (https://guide.meteor.com/) clearly encourages using NPM packages when possible since many Atmosphere packages are simpler wrapper around a NPM package.

But can also poorly choose NPM packages, thus the mistake in this case is on the poor choice of third party packages by the developer and not on the framework.

[vlasky]

Were you using Atmosphere packages?

Ever since Meteor added native support for NPM packages, many Meteor package developers are only publishing them as NPMs instead of on Atmosphere. That might be why you believe that there's rot.