I'm trying to edit a package.Json

[DanielSusser]

I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• [ x] npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

How can the CLI team reproduce the problem?

https://preview.c9users.io/dsuss/fcc_how-to-npm_1/project_folder/npm-debug.log
<! - - Please a complete description of how to reproduce the problem.
Include a gist of your npm-debug.log file.
If you've never used gist.github.com, start here:
https://github.com/EmmaRamirez/how-to-submit-your-npm-debug-log
-->

supporting information:

• npm -v prints:
• node -v prints:
• npm config get registry prints:
• Windows, OS X/macOS, or Linux?:
• 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).

[kenany]

If you want to edit your package.json file, you can do so via your favorite text editor.

[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.