Node.js 使用npm错误安装程序包

我在这里遵循npm文档来学习如何正确使用它，我成功地下载了正确的节点和npm，正确地检查了版本，然后我将npm的默认目录更改为另一个目录，现在是这样的：

MacBook-Pro-2:~ macetti$ npm config get prefix
/Users/macetti/npm-global

问题是，当我尝试使用此命令安装时

npm install lodash

出现这个

npm ERR! Darwin 14.4.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "lodash"
npm ERR! node v0.12.4
npm ERR! npm  v2.10.1

npm ERR! error:0906D06C:PEM routines:PEM_read_bio:no start line
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/macetti/npm-debug.log

这里是我的npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/local/bin/npm', 'install', 'lodash' ]
2 info using npm@2.10.1
3 info using node@v0.12.4
4 verbose config Skipping project config: /Users/macetti/.npmrc. (matches userconfig)
5 verbose install initial load of /Users/macetti/package.json
6 verbose readDependencies loading dependencies from /Users/macetti/package.json
7 silly cache add args [ 'lodash', null ]
8 verbose cache add spec lodash
9 silly cache add parsed spec { raw: 'lodash',
9 silly cache add   scope: null,
9 silly cache add   name: 'lodash',
9 silly cache add   rawSpec: '',
9 silly cache add   spec: '*',
9 silly cache add   type: 'range' }
10 silly addNamed lodash@*
11 verbose addNamed "*" is a valid semver range for lodash
12 silly addNameRange { name: 'lodash', range: '*', hasData: false }
13 silly mapToRegistry name lodash
14 silly mapToRegistry using default registry
15 silly mapToRegistry registry https://registry.npmjs.org/
16 silly mapToRegistry uri https://registry.npmjs.org/lodash
17 verbose addNameRange registry:https://registry.npmjs.org/lodash not in flight; fetching
18 verbose request uri https://registry.npmjs.org/lodash
19 verbose request no auth needed
20 info attempt registry request try #1 at 09:54:46
21 verbose request id f688faead59da217
22 http request GET https://registry.npmjs.org/lodash
23 verbose stack Error: error:0906D06C:PEM routines:PEM_read_bio:no start line
23 verbose stack     at Error (native)
23 verbose stack     at Object.createSecureContext (_tls_common.js:108:19)
23 verbose stack     at Object.exports.connect (_tls_wrap.js:852:21)
23 verbose stack     at Agent.createConnection (https.js:82:14)
23 verbose stack     at Agent.createSocket (_http_agent.js:194:16)
23 verbose stack     at Agent.addRequest (_http_agent.js:166:23)
23 verbose stack     at new ClientRequest (_http_client.js:154:16)
23 verbose stack     at Object.exports.request (http.js:49:10)
23 verbose stack     at Object.exports.request (https.js:136:15)
23 verbose stack     at Request.start (/usr/local/lib/node_modules/npm/node_modules/request/request.js:963:30)
24 verbose cwd /Users/macetti
25 error Darwin 14.4.0
26 error argv "node" "/usr/local/bin/npm" "install" "lodash"
27 error node v0.12.4
28 error npm  v2.10.1
29 error error:0906D06C:PEM routines:PEM_read_bio:no start line
30 error If you need help, you may report this error at:
30 error     <https://github.com/npm/npm/issues>
31 verbose exit [ 1, true ]

我在寻找解决问题的方法，我尝试了好几种方法，但都没有解决问题

有人能帮我吗

非常感谢

根据，与NPN安装相反，出现的类似问题与安装包有关。我会在供应商lodash上记录问题，以解决错误

参考npm/issues/8734：

./bin/www  must exists and contains valid  index.js  file.
You can change folder value for  start  property.

I think it's not a NPM issue, please close this issue.
Go on StackOverflow or Google something like  express npm start node ./bin/www 

I hope I have helped you.

及

---

我想按照你写的做，在/usr/local/bin上没有文件夹www，所以我创建了它，并在里面放了index.js。理论上这应该在安装过程中创建，不是吗？对不起，a应该在index.js上放什么内容？我不知道是否npm问题，但我只是按照npm文档上的解释，知道我不能安装任何软件包，我尝试使用不同的软件包，但结果是一样的。你能帮我解决这个问题吗？你认为应该像一开始那样将权限文件夹设置为默认值更好吗？现在是/Users/macetti/npm global可能是问题所在？我一步一步地修改它，没有出现任何错误，但在更改权限文件夹之前，我成功地安装了一个包。包是您自己编写的还是由第三方编写的？是的，我更改了标题，是错误的吗？当我写这篇文章的时候，我认为问题出在npm上，你们说那个是我想更改标题的软件包，以便有人能帮助我。如果你认为是错误的，我可以删除它，并创建一个新的问题，但我不理解的意义，关闭这个问题，并重新打开一个新的标题，反正我是新的，我接受，如果你告诉我，这将更好。对不起，我不能提供更多。以前没有这个问题，但我可以帮忙。

After install do  npm install -g npm@2.12.1 .

Check your version with  npm -v .

If the problem persist, your issue concern  express  or your package configuration not npm.