How I Work Around The require(“../../../../../../../”) Problem In NodeJS

#1

Post by docluv » Thu, Feb 20, 2014, 12:40 PM UTC

How I Work Around The require(“../../../../../../../”) Problem In NodeJS
lostechies.com

Re: How I Work Around The require(“../../../../../../../”) Problem In NodeJS

#2

Post by unwind » Thu, Feb 20, 2014, 1:34 PM UTC

The article seems to be missing crucial examples, making it very hard to read and follow. :/

Re: How I Work Around The require(“../../../../../../../”) Problem In NodeJS

#3

Post by tlarkworthy » Thu, Feb 20, 2014, 1:36 PM UTC

can't you install a private npm module by npm link? That won't touch the npm servers [1].

Then your other project in the same file system can just require like a first class public npm module.

[1] https://www.npmjs.org/doc/cli/npm-link.html

Re: How I Work Around The require(“../../../../../../../”) Problem In NodeJS

#4

Post by heydenberk » Thu, Feb 20, 2014, 1:41 PM UTC

Setting an environment variable to include a directory in which you have libraries that you need to use across your application is not a workaround. It's using a feature.

Re: How I Work Around The require(“../../../../../../../”) Problem In NodeJS

#5

Post by joel_perl_prog » Thu, Feb 20, 2014, 1:46 PM UTC

I've done this in the past on *nix systems, for Perl. I modified PERL5LIB from my .bashrc file, so that my project lib was looked for by default. This, rather than having to put 'use lib '../../../yikes/ugly' ahead of any inclusion of project modules.

Another approach, which I favor now, is to place modules directly into the default locations, such as /usr/lib/share/perl5 and etc.--usually there are a number of paths Perl looks at by default. It's then just a matter of saying 'use MyModule;' in code.

Is node.js similar, in having one or more include paths set by default, and could files be put there, to where you never have to refer to something by relative location again?

Re: How I Work Around The require(“../../../../../../../”) Problem In NodeJS

#6

Post by jbeja » Thu, Feb 20, 2014, 1:48 PM UTC

How this would work with browserify?

Re: How I Work Around The require(“../../../../../../../”) Problem In NodeJS

#7

Post by Touche » Thu, Feb 20, 2014, 1:55 PM UTC

Article appears to be down.

I've never worked on a Node project with directories that nested more than 3 or 4 levels deep, so I don't see this as a "problem" (but maybe the article makes a case that it is).

Re: How I Work Around The require(“../../../../../../../”) Problem In NodeJS

#8

Post by camus2 » Thu, Feb 20, 2014, 1:58 PM UTC

tlarkworthy wrote: post #3

can't you install a private npm module by npm link? That won't touch the npm servers [1]. Then your other project in the same file system can just require like a first class public npm module. [1] https://www.npmjs.org/doc/cli/npm-link.html

The OP did not read npm doc obviously. npm link is the killer feature of npm.

Re: How I Work Around The require(“../../../../../../../”) Problem In NodeJS

#9

Post by alexandere » Thu, Feb 20, 2014, 1:59 PM UTC

http://webcache.googleusercontent.com/search?q=cache:http://...

Re: How I Work Around The require(“../../../../../../../”) Problem In NodeJS

#10

Post by royjacobs » Thu, Feb 20, 2014, 2:04 PM UTC

tlarkworthy wrote: post #3

can't you install a private npm module by npm link? That won't touch the npm servers [1]. Then your other project in the same file system can just require like a first class public npm module. [1] https://www.npmjs.org/doc/cli/npm-link.html

How do you go about setting these links when you freshly checked out a project through source control? There is no "npm link all", is there?