Javascript 上一版本npm（和节点）的未满足依赖项

我有最新版本的npm和node。我有以下错误/警告：

$ npm --version
2.4.1

$ node --version
v0.10.36

$ npm install

> my_project@0.0.0 preinstall /Users/alex/Documents/projects/ruby/my_project
> script/gem_npm install

npm WARN package.json karma-ie-launcher@0.1.5 No README data
npm WARN package.json karma-qunit@0.1.4 No README data
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/node-sass requires mkdirp@'~0.3.5' but will load
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/mkdirp,
npm WARN unmet dependency which is version 0.5.0
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/testem requires js-yaml@'~0.3.5' but will load
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/js-yaml,
npm WARN unmet dependency which is version 3.2.5
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/testem requires glob@'~3.1.21' but will load
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/glob,
npm WARN unmet dependency which is version 3.2.11
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/karma requires glob@'~3.1.21' but will load
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/glob,
npm WARN unmet dependency which is version 3.2.11
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/karma requires lodash@'~1.1' but will load
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/lodash,
npm WARN unmet dependency which is version 2.4.1
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/karma-coffee-preprocessor/node_modules/coffee-script requires mkdirp@'~0.3.5' but will load
npm WARN unmet dependency /Users/alex/Documents/projects/ruby/my_project/node_modules/mkdirp,
npm WARN unmet dependency which is version 0.5.0

---

如何解决这些问题？

这是一个已知的问题，npm的依赖项解析有点不正确，请参见此处：

最简单的解决方法是手动安装依赖项，或构建package.json，以便在依赖项模型之前列出任何与其他模块相关的顶级模块

---

e、 g:

npm安装从日志中提取的mkdirp@'~0.3.5'

。

删除node\u modules文件夹

rm -rf node_modules/

再次运行

npm安装