vendredi 8 septembre 2017

Writing a path in package.json dependencies duplicate it

basically I have a package.json in my app, nothing unusual, and in the dependencies of this package.json, I have a link to a module that I created with ember-engines, a module that permit to create addon-like repository, but with a bunch of utility for Ember.js.

My package.json

{
  "name": "web",
  "version": "0.0.0",
  "description": "Small description for web goes here",
  "private": true,
  "directories": {
    "doc": "doc",
    "test": "tests"
  },
  "repository": "",
  "engines": {
    "node": ">= 0.12.0"
  },
  "author": "",
  "license": "MIT",
  "dependencies": {
    // Bunch of dependencies 
    "myAddon": "../myApp-web-addons/myAddon",
  },
}

My repository look like that:

repository
 | 
 | -- myApp-web-addons
 |       |
 |       | -- myAddon
 |              |
 |              | -- nodes_modules, index.js, config, ect...
 |              | -- package.json
 |
 | -- myApp
        |
        | -- nodes_modules, index.js, config, ect...
        | -- package.json

Normally, as you can see the path in my package.json is good, but when I run npm install, I receive this error:

npm ERR! code ENOLOCAL
npm ERR! Could not install from "../leosac-web-addons/leosac-web-addons/evoxs" 
         as it does not contain a package.json file.

I don know if I do something wrong, but for me everything seems fine, and if you are using ember-engines, this is the right method to call an addon in your Application.

If anybody know why it does that, I'll be very thankful!!




Aucun commentaire:

Enregistrer un commentaire