I can confirm that npm downgrading to npm@4 solves this issue.
Had the same one.. Maybe it's worth to mention it at the release page.

Thank you @PitaJ