Sorry to say but such frameworks and ideas are from the last decade (Rails was the main reason why I switched to Node).
This is something that I spend a lot of time thinking about (for instance, how can we apply this to the organization of corporations?)..
The point of npm is ... to be a package manager.
Express is a framework. I admittedly don't know much about it, but I believe it basically has pluggable middleware, like Rails.
Not sure these things share the "point" you are claiming they do.
It's great Node has both framework choices and a wealth of small modules that do one thing. I think there's room for both.
I love Node, and am consistently impressed by npm, but pretending that these technologies represent a "paradigm shift" and some sort of cohesive shift away from frameworks is faintly ridiculous.
If you work on a team and are faced with the task of creating a large app your choice is to pick a framework or create your own from libraries. I'd argue that a (good) framework is likely to be better because the conventions are likely clearer and better documented than anything you cook up yourself by combining libraries and filling in gaps with your own code.