From these graphs we could come up with some reasonable boundaries. Packages that:
- have more than one version: 71853
- are over two weeks old: 42106
- had a new release in the last 360 days: 71277
There are 31888 packages satisfying all three conditions above. Though itβs only one third of all packages there, the amount is still enormous.
Now, if only I could search those 31,888 packages on NPM alone if I wanted to.
EDIT: By the way, for anybody reading this article not familiar with the JavaScript ecosystem, this is interesting:
Mocha is clearly the most popular test framework, while nodeunit is way behind. And no-one seems to use Jasmine.
Jasmine appears to be unpopular within the JavaScript community but in reality that just accounts for those in the NodeJS and, more recently, the subset of the front-end JS community who use NodeJS tools in their projects.
Mocha, the most popular test framework, has been a Node module since late 2011 [0], whereas Jasmine has only been one since mid-2013 [1]. I have a hunch that the majority of Jasmine users aren't on-board with the movement of front-end JS and NodeJS ecosystems merging, and since Jasmine [3] doesn't really aim itself at NodeJS projects, it's far less likely to be used in any project which uses NPM for dependency management.
Jasmine is hopeless for serious node apps, that's why. It lacks critical features that are long standing and bitterly complained about by node developers due to the hostile and half-assed responses from the maintainers to those issues.
EDIT: By the way, for anybody reading this article not familiar with the JavaScript ecosystem, this is interesting:
Jasmine appears to be unpopular within the JavaScript community but in reality that just accounts for those in the NodeJS and, more recently, the subset of the front-end JS community who use NodeJS tools in their projects.Mocha, the most popular test framework, has been a Node module since late 2011 [0], whereas Jasmine has only been one since mid-2013 [1]. I have a hunch that the majority of Jasmine users aren't on-board with the movement of front-end JS and NodeJS ecosystems merging, and since Jasmine [3] doesn't really aim itself at NodeJS projects, it's far less likely to be used in any project which uses NPM for dependency management.
Not really that important, just interesting :)
[0]: https://github.com/visionmedia/mocha/commits/master/package....
[1]: https://github.com/pivotal/jasmine/commits/master/package.js...
[2]: https://github.com/pivotal/jasmine