I have the same problem as #18 This issue does not exist in the live demo, but npm v2.0.6 is not fixed