Sometimes the value to customers is just a system that works without downtime or failures, and the next increase in value is not even related to something that was built on this bleeding-edge packaging model. The only types of development projects that seem to benefit from it are the kind of project that can dedicate a full-time or mostly-full-time developer to it forever (forever being the lifetime of the product/service).
If dependency issues crop up every few months for a perodically updated project that could almost be a death knell, if you have to pivot or do major work on the backend all of a sudden you could come back to just a broken set of shambles. So the only thing it fits is a really strange gap between hobbyist/side project and stable production which ends up being just plain risky for a technology choice.
IMHO Node isn't built on this mindset ( endless churn ). I think it's just rapidly evolving. It's just enthusiasm by the community.
As far as my experience goes, I just put more effort in finding the right module rather than finding >any< module that will do the work. Afterwards I can usually npm-shrinkwrap, upload to DigitalOcean and leave forever.
And no. Things break all the time and still give value to customers. Things break for A reason and still give value to customers.
Yep it would be cool and more non-breaking if 20-years of Java experience was injected into NodeJS, but I bet in 20-years NodeJS will be even better than the popular alternatives these days.