> is just shooting yourself in the foot in a future time, as this has shown only because of a design oversight by npm which is now being fixed. Like I said, fi

> is just shooting yourself in the foot in a future time, as this has shown only because of a design oversight by npm which is now being fixed. Like I said, fix the issues in handling your dependencies, and you remove the overhead of including them, such that "depending on several hundred things" is managing it. Checking your needed dependencies into your source tree can either be done by recreating them in your source tree or pointing to them. Your pick.