Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

npm WARN saveError ENOENT: no such file or directory, open 'C:\xampp\htdocs\package.json' npm WARN enoent ENOENT: no such file or directory, open 'C:\xampp\htdocs\package.json' npm WARN htdocs No description npm WARN htdocs No repository field. npm WARN htdocs No README data npm WARN htdocs No license field. #18910

Closed
13 tasks
Sharif-Mohammad opened this issue Oct 20, 2017 · 1 comment
Labels

Comments

@Sharif-Mohammad
Copy link

I'm opening this issue because:

  • npm is crashing.
  • npm is producing an incorrect install.
  • 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?

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 kenany added the support label Oct 20, 2017
@kenany
Copy link
Contributor

kenany commented Oct 20, 2017

Closing since the issue body is blank.

@kenany kenany closed this as completed Oct 20, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants