Skip to content

Could not install globally with NPM #13

Description

@AcelisWeaven

Hi,

I couldn't install the package by running the command npm install -g nelson.gui.

Error output (taken from Windows, but identical with an Ubuntu):

npm ERR! path C:\Users\...\AppData\Roaming\npm\node_modules\nelson.gui\build\nelson.gui.js
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod 'C:\Users\...\AppData\Roaming\npm\node_modules\nelson.gui\build\nelson.gui.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\...\AppData\Roaming\npm-cache\_logs\2018-05-10T19_00_47_085Z-debug.log

The issue seems to be that the file build/nelson.gui.js doesn't exist at this point, and cannot be chmoded (and then bin-linked). Running npm install -g nelson.gui --no-bin-links doesn't trigger the error.

Everything seems fine when the package.json is changed to use the file src/nelson.gui.js instead. (see PR #12)
I don't know if it could have any side effect.

Tested with:

  • Windows 10 / Node 8.11.1 / npm 5.6.0
  • Ubuntu 16.04 / Node 8.11.1 / npm 6.0.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions