the npm error

[fengkx]

I'm opening this issue because:

• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

I am using hexo ,but it crash. And the bash say it is npm erro

How can the CLI team reproduce the problem?

0 info it worked if it ends with ok

1 verbose cli [ '/home/fengkx/.nvm/versions/node/v8.2.1/bin/node',
1 verbose cli '/home/fengkx/.nvm/versions/node/v8.2.1/bin/npm',
1 verbose cli 'install',
1 verbose cli 'hexo-deployer-git',
1 verbose cli '–save' ]
2 info using npm@5.3.0
3 info using node@v8.2.1
4 verbose config Skipping project config: /home/fengkx/.npmrc. (matches userconfig)
5 verbose npm-session 6117826d45f919fb
6 silly install loadCurrentTree
7 silly install readLocalPackageData
8 silly fetchPackageMetaData error for hexo-deployer-git@latest install hexo-deployer-git –save is not a legal HTTP header value
9 error cb() never called!
10 error This is an error with npm itself. Please report this error at:
11 error https://github.com/npm/npm/issues

supporting information:

• npm -v prints:5.3.0
• node -v prints:v8.2.1
• npm config get registry prints:https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?:Ubuntu
• Network issues:
  • Geographic location where npm was run:
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don't use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

[npm-robot]

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining WeAllJS and asking your question in its #npm channel. The npm CLI team is all present there, but there are also lots of other folks who can help you too.

For more information about our new issue aging policies and why we've instituted them please see our blog post.