mscdex asked about my version. I am running 0.10.29 - the latest.
I did further investigation:  looking thru node-gyp issues  it looks like 
there are some unresolved issues related to permissions on Unix.
Just out of curiosity I moved the package.json from ./lib directory under 
node-gyp to the parent directory (node-gyp). The process got further but 
then it ran into an issue updating  /myroot/.node-gyp.
So overall, the explanation I got to my original question helped me 
understand how require works - thanks.
But as these things go I am still without an answer to my originalproblem - 
I will turn to the node-gyp issues on github seeking more information 
(although it looks like everyone is stymied by a variety of permission 
related issues on Linux). I might go looking for an Unix guru in my 
organization to help sort this out.

Thanks for the help.

On Monday, July 14, 2014 8:56:58 AM UTC-4, Deva Kumaraswamy wrote:
>
> Ok. That makes sense.
> I am checking thru the directories and comparing what I have on my Centos 
> box with what is on my windows box. when I get into work,  I will run the 
> debugger to see why it is failing - hpefully it is something as simple as 
> permissions.:-)
> thanks...
>
> On Monday, July 14, 2014 1:39:23 AM UTC-4, Ryan Graham wrote:
>>
>> It's only index.js by default. If there is a package.json in that 
>> directory it is used to look up the package's "main" entry point. It 
>> defaults to "index.js", but it is often something like "lib/<someclass>.js".
>>
>> ~Ryan
>>
>> On Sat, Jul 12, 2014 at 8:01 PM, Deva Kumaraswamy <[email protected]> 
>> wrote:
>>
>>> Thanks. That is pretty nifty. However:
>>> I do not see an index.js in the npm->node->modules->node-gyp directory 
>>> or any of its sub directories. 
>>> My directories on windows looks the same.
>>> Still puzzled, 
>>>
>>> Subnote: There is a node-gyp entry in the lib directory that exports the 
>>> entries the failing code seems to be looking for. 
>>>
>>>
>>> On Friday, July 11, 2014 6:59:48 PM UTC-4, mgutz wrote:
>>>>
>>>> require('../') means require parent directory's index.js. When a 
>>>> require path is a directory, node tries index.js.
>>>>
>>>>
>> -- 
>> http://twitter.com/rmgraham 
>>
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/0775d7fe-5c3b-4a7f-aa16-1cb9d9306d88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to