Am 24.06.12 20:11, schrieb Christoph Iserlohn: > This is a bug. I'm working on it. > Should be fixed in 1.1.32_1. Please upgrade again: $ sudo port selfupdate && sudo port upgrade npm -- Christoph