Problems with local modules installing flowdata

[366256]

Hi,

this might not be the best place for this issue, but I couldn't find any other thread which discusses this problem. I figured, that you might have a solution.

When I want to install flowdata, I always get the error that npm cannot install the local dependencies:

npm ERR! addLocal Could not install .../flowdata@0.2.1/local_modules/logging
npm ERR! addLocal Could not install .../flowdata@0.2.1/local_modules/utils
npm ERR! addLocal Could not install .../flowdata@0.2.1/local_modules/inheritable
npm ERR! Darwin 14.1.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.10.32
npm ERR! npm  v2.6.1
npm ERR! path .../flowdata@0.2.1/local_modules/logging
npm ERR! code ENOENT
npm ERR! errno 34

npm ERR! enoent ENOENT, open .../flowdata@0.2.1/local_modules/logging'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! Please include the following file with any support request:
npm ERR!     ..../npm-debug.log

I've tried cloning the repository, build it and link it in the global space, but this didn't work out.

I'm running MAC OSX Yosemite with npm 2.6.1.

Thanks in advance!

[code-vicar]

Hmm, interesting. I'll look into it.
Thanks.

[code-vicar]

The 'local_modules' are setup as local file dependencies in package.json. They are bundled with the project. When npm is installing it will look for them in the './local_modules/' path relative to the package.json. Looks like for some reason your clone is either missing the local_modules folder or doesn't have permission to read it. Can you verify that the 'local_modules' folder and all sub folders are in your clone and that they are readable?

[366256]

I don't know the internals of npm, but it looks like, that npm won't create the folder flowdata@0.2.1 (relative to my project) at all. Based on the logs, it seems like, that it should create a temporary copy of flowdata relative to the location where I execute the npm installcommand. However, monitoring the folder while installing shows, that no folder will be created.

I monitored the global package folder of npm /usr/local/lib/node_modules while installing and found out, that flowdata will be checked out to this location.

I suspect, that the relative path in the package json to the local modules is relative to the location where I execute the npm install, not the location where npm put's the package globally /usr/local/lib/node_modules and therefore cannot find the local modules.

[code-vicar]

Ah, I hadn't tried installing the module globally. You're right, it doesn't look like using local_modules in this manner (with 'file:' dependencies in package.json) will work. I'll change this up and try a different solution.
Thanks.

[code-vicar]

Alright, I got past the issue with the local_modules, but installing globally is still not working. This time the installation will go into and endless recursion while trying to resolve the 'odata' dependency. Seems like something the olingo team did is preventing this from installing properly as a global.

[366256]

I ran in the same problems installing the odata dependency. That's why I looked for alternatives and tried using flowdata :)