[Bug 196255] New: [patch] www/npm chokes on many packages

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196255

            Bug ID: 196255
           Summary: [patch] www/npm chokes on many packages
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: adamw at FreeBSD.org

npm 2.1.14 chokes on empty paths present in many packages. This means that if
any of the offending packages are installed before the upgrade to 2.1.14, npm
will completely stop working. It can't update the packages, nor can it
uninstall them. If you delete and reinstall them, then npm will stop working
again.

[adamw at apnoea ~] npm -g outdated
npm ERR! FreeBSD 10.1-RELEASE-p3
npm ERR! argv "node" "/usr/local/bin/npm" "-g" "outdated"
npm ERR! node v0.10.33
npm ERR! npm  v2.1.14

npm ERR! Object.keys called on non-object
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <http://github.com/npm/npm/issues>
npm ERR! FreeBSD 10.1-RELEASE-p3
npm ERR! argv "node" "/usr/local/bin/npm" "-g" "outdated"
npm ERR! node v0.10.33
npm ERR! npm  v2.1.14

npm ERR! Object.keys called on non-object
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <http://github.com/npm/npm/issues>
npm ERR! FreeBSD 10.1-RELEASE-p3
npm ERR! argv "node" "/usr/local/bin/npm" "-g" "outdated"
npm ERR! node v0.10.33
npm ERR! npm  v2.1.14

(repeats over and over and over)

There is an active npm bug about this: https://github.com/npm/npm/issues/3443

That bug also contains a patch:
https://github.com/npm/npm/commit/aa2ea543e080461521cc1235d971284f012aae63

I've applied that patch and I can confirm that it fixes the problem.

[adamw at apnoea ~] npm -g outdated
Package                    Current  Wanted  Latest  Location
mkdirp                       0.3.5   0.3.5   0.5.0

That patch will be in the next release, but please consider applying it before
then, as I suspect I'm not the only person bitten by this bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.