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

Unable to locate ---- /home/iota/iota-pm.conf #19445

Closed
10 tasks
Bernie-2017 opened this issue Dec 22, 2017 · 2 comments
Closed
10 tasks

Unable to locate ---- /home/iota/iota-pm.conf #19445

Bernie-2017 opened this issue Dec 22, 2017 · 2 comments
Labels

Comments

@Bernie-2017
Copy link

I'm opening this issue because:

  • [ x] npm is crashing.
  • [ x] 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?

supporting information:

  • npm -v prints: 3.5.2
  • node -v prints: v4.2.6
  • npm config get registry prints: https://registry.npmjs.org/
  • Windows, OS X/macOS, or Linux?: 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).
@kenany kenany added the support label Dec 22, 2017
@kenany
Copy link
Contributor

kenany commented Dec 22, 2017

@Bernie-2017 Could you please take the time to fill out the support form in your post? Thanks!

@kenany
Copy link
Contributor

kenany commented Jun 11, 2018

Closing since the issue body is still blank.

@kenany kenany closed this as completed Jun 11, 2018
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