Cloud9 I guess would be a good example of a killer app ,but that's no CMS.
The reason why there is no serious CMS with node is that nodejs development is extremely hard, because async programming is hard. No matter how much layers one puts on top of it (promises,generators...) you can't abstract async programming in nodejs.
Look at Go, Go routines can be totally abstracted. IF I write that code:
result := Object.DoNonBlocking()
As a client of Object I don't have to know whether it is run concurrently, or not , or blocking or not. In node I have to know whether I returns a promise or a value , IE hump into the event loop or not.PHP has its share of problems though,just like Go, but their concurrency model(or lack of) make things way more easy.
I can't imagine writing something such as Magento or Drupal in nodejs (with the exact same features). It would be just insane. A great challenge though.
At this time Javascript's biggest strength is build tools. It may not be as mature as PHP on the server, but there is so much community growth that I don't think it will be long catching up.
The fact that there's at least 4 "mainstream" build tools and their popularity changes every 6 months is a sign of an ecosystem with little stability that is no good to build a solid foundation.
On Ruby and Python land, how long has it been since RoR and Django have been the dominant players?
No, not when I have access to all kinds of other languages, frameworks, libraries, etc to choose from on the server side.
- Minification: Uglify
- Transpilation: Babel/TypeScript/CoffeeScript
- JS Module Systems: Require/Browserify/Webpack/JSPM
- CSS preprocessors: Less/Sass/Stylus
- Linting: JSHint/ESLint/CSSLint
If you're using a lot of front-end tools, you're using Node. And if you're using Node, you might as well use it to write your APIs.