Package: npm
Version: 1.1.4~dfsg-2
Severity: normal

Short summary:

$ npm -g get prefix
$ sudo npm -g get prefix

I've tried to investigate what's going on, but have gotten lost in the maze of
npm configuration files. I suspect that the tweak that Debian's done to split
the prefix where npm is installed from the prefix where npm installs packages
isn't quite working right.

This is making impossible for a script I'm trying to write to determine where
the global modules are installed.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages npm depends on:
ii  node-abbrev       1.0.3-1
ii  node-fstream      0.1.13-1
ii  node-graceful-fs  1.1.8-1
ii  node-ini          1.0.2-1
ii  node-minimatch    0.2.0-1
ii  node-mkdirp       0.3.1-2
ii  node-node-uuid    1.3.3-1
ii  node-nopt         1.0.10-2
ii  node-request      2.9.153-1
ii  node-rimraf       2.0.1-1
ii  node-semver       1.0.13-2
ii  node-tar          0.1.13-1
ii  node-which        1.0.5-1
ii  nodejs            0.6.19~dfsg1-5
ii  nodejs-dev        0.6.19~dfsg1-5

npm recommends no packages.

Versions of packages npm suggests:
ii  build-essential  11.5

-- no debconf information

Pkg-javascript-devel mailing list

Reply via email to