Having smaller packages each with many dependencies is a common node design pattern. I think this started because it doesn't have a lot of framework code to re

Having smaller packages each with many dependencies is a common node design pattern. I think this started because it doesn't have a lot of framework code to relay on, so simpler functions became packages. It has advantages and disadvantages. People concerned about production uptime/deployment should keep copies of all dependencies on their network, and run npm against their network repo.