Re:How I Work Around The require(“../../../../../../../”) Pr...
by camus2 on Thursday February 20, 2014 @08:58AM
(#7270711)
The OP did not read npm doc obviously. npm link is the killer feature of npm.
Re:How I Work Around The require(“../../../../../../../”) Pr...
by Jare on Thursday February 20, 2014 @09:17AM
(#7270806)
I don't think npm link is meant to be used in production like that.
Re:How I Work Around The require(“../../../../../../../”) Pr...
by 2mur on Thursday February 20, 2014 @11:20AM
(#7271594)
You probably shouldn't be using npm for production builds. npm is good for libraries, but applications should probably be tarballed.
Re:How I Work Around The require(“../../../../../../../”) Pr...
by Jare on Thursday February 20, 2014 @05:41PM
(#7274195)
That was point of the article: npm is not a valid option for various reasons, but it should be easier for applications to organize the source code in multiple directories which you then tarball.
Re:How I Work Around The require(“../../../../../../../”) Pr...
by royjacobs on Thursday February 20, 2014 @09:04AM
(#7270742)
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?
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