Problems with long paths in npm
I've been struggling for a long time with npm because it keeps all downloaded packages and its dependencies in a deep tree-like structure and therefore exceeds allowed 260 characters restriction for paths. As a result most of the tooling doesn't work properly. MSBUILD wildcard search is failing without visible symptoms when long paths exist. CruiseControl cannot cleanup workspace because of long paths. TFS is failing to compare files for the same reason. I really can't understand how such an issue could exist in a world-known package manager. Fortunately, I've got to know that npm@3 is coming where this problem is fixed. In this release npm flattens folder-structure eliminating long paths. I've tested this and it really works. I'm happy this problem will be solved at last soon.