Issue with permissions in a node.js module

Question

I built an npm module named emeraldfw and published it. My package.json file is

{
  "name": "emeraldfw",
  "version": "0.6.0",
  "bin": "./emeraldfw.js",
  "description": "Emerald Framework is a language-agnostig web development framework, designed to make developer's lives easier and fun while coding.",
  "main": "emeraldfw.js",
  "directories": {
    "example": "examples",
    "test": "test"
  },
  "scripts": {
    "test": "mocha"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/EdDeAlmeidaJr/emeraldfw.git"
  },
  "keywords": [
    "web",
    "development",
    "framework",
    "language",
    "agnostic",
    "react"
  ],
  "author": "Ed de Almeida",
  "license": "MIT",
  "bugs": {
    "url": "https://github.com/EdDeAlmeidaJr/emeraldfw/issues"
  },
  "homepage": "https://github.com/EdDeAlmeidaJr/emeraldfw#readme",
  "devDependencies": {
    "jshint": "^2.9.4",
    "mocha": "^3.3.0"
  },
  "dependencies": {
    "jsonfile": "^3.0.0",
    "react": "^15.5.4",
    "vorpal": "^1.12.0"
  }
}

As you may see, I declared a "bin": "./emeraldfw.js" binary, which corresponds to the application itself. The package.json documentations says this is going to create a link to the application executable at node.js bin/ directory. This worked fine, but when I install it globally (npm install emeraldfw -g) and then run it from the command line I receive an error messsage

All other node modules are working fine and my application is passing in all tests and when I run it directly inside the development directory (with node emeraldfw.js) it works really fine.

I'm not a node.js expert and after having fought this error for two days, here I am to ask for help.

Any ideas?

EDIT:

I checked the permissions for my node binary (emeraldfw.js) and it belongs to edvaldo:edvaldo, my user and group. And it is with executable permissions set. I should have no permission issues inside my own area with these settings, don't you think?

Answer 1

Well, shebang issue here.

Before creating npm modules, you need read every single line of it's documentation.

As it stated here you need to use shebang to let your operating system know that it should run with node instead of operating system's own script execution hosts.

Please make sure that your file(s) referenced in bin starts with #!/usr/bin/env node, otherwise the scripts are started without the node executable!

So, by using shebang on an npm module, you tell the os to create platform specific executables which let it use node to run the script. A .cmd file on Windows for example.

Answer 2

Have you try to install as su?