https://pantsbuild.org/ logo
Powered by
#general
  • b

    bored-art-40741

    08/27/2015, 1:26 AM
    We specifically wanted to fix the old bug in parallel artifact cache downloads by using a go wrapper, ha
  • e

    enough-analyst-54434

    08/27/2015, 1:26 AM
    The interface is ugly - sure
  • e

    enough-analyst-54434

    08/27/2015, 1:26 AM
    but presumably there would be O(1) of these
  • b

    bright-dinner-81701

    08/27/2015, 1:26 AM
    im saying what i did is ugly
  • b

    bright-dinner-81701

    08/27/2015, 1:27 AM
    the npm thing i just did
  • e

    enough-analyst-54434

    08/27/2015, 1:28 AM
    aha
  • e

    enough-analyst-54434

    08/27/2015, 1:28 AM
    so @bright-dinner-81701 what was the ugly way?
  • b

    bright-dinner-81701

    08/27/2015, 1:30 AM
    ok so you can use your trick and "npm install webpack -g —prefix /fake/global/path"
  • b

    bright-dinner-81701

    08/27/2015, 1:31 AM
    that will give you an isolated install of webpack, with its full dep tree (as there arent any other modules already under /fake/global/path/node_modules that would prevent it from installing its own deps)
  • b

    bright-dinner-81701

    08/27/2015, 1:31 AM
    then
  • b

    bright-dinner-81701

    08/27/2015, 1:31 AM
    in your project
  • b

    bright-dinner-81701

    08/27/2015, 1:31 AM
    mkdir node_modules && mkdir node_modules/.bin
  • b

    bright-dinner-81701

    08/27/2015, 1:33 AM
    ln -s /fake/global/path/node_modules/webpack node_modules/webpack ln -s /fake/global/path/bin/webpack node_modules/.bin/webpack
  • b

    bright-dinner-81701

    08/27/2015, 1:33 AM
    then do your normal “npm install"
  • e

    enough-analyst-54434

    08/27/2015, 1:33 AM
    can;t we use npm link for that?
  • e

    enough-analyst-54434

    08/27/2015, 1:33 AM
    with --prefix
  • e

    enough-analyst-54434

    08/27/2015, 1:33 AM
    that was my handwave
  • e

    enough-analyst-54434

    08/27/2015, 1:34 AM
    ie: in your project
  • b

    bright-dinner-81701

    08/27/2015, 1:34 AM
    weirdly, npm link works slightly differently, and more importantly no matter what i do it retriggers the C compilation
  • e

    enough-analyst-54434

    08/27/2015, 1:34 AM
    npm link --prefix /fake/webpack/global/path link webpack
  • e

    enough-analyst-54434

    08/27/2015, 1:34 AM
    k
  • b

    bright-dinner-81701

    08/27/2015, 1:35 AM
    First, npm link in a package folder will create a globally-installed symbolic link from prefix/package-name to the current folder (see npm-config(7) for the value of prefix). Next, in some other location, npm link package-name will create a symlink from the local node_modules folder to the global symlink.
  • b

    bright-dinner-81701

    08/27/2015, 1:35 AM
  • b

    bright-dinner-81701

    08/27/2015, 1:35 AM
    it works slightly differently than an install -g
  • e

    enough-analyst-54434

    08/27/2015, 1:35 AM
    but 1st npm link in the webpack
  • e

    enough-analyst-54434

    08/27/2015, 1:35 AM
    with no args
  • e

    enough-analyst-54434

    08/27/2015, 1:35 AM
    then in all users, npm link webpack --prefix
  • e

    enough-analyst-54434

    08/27/2015, 1:36 AM
    I'm just using npm help [cmd]
  • e

    enough-analyst-54434

    08/27/2015, 1:36 AM
    again - handwave, I need to shut up and try things for real after the RB post
  • e

    enough-analyst-54434

    08/27/2015, 1:37 AM
    Basically, I'm keying off the 1st sentences:```
1...229230231...2420Latest