@hashingbob @nodejs @heroku It appears to be an npm issue. Running npm install -d locally gives the same error.
