Closed jevawin closed 6 years ago
Thanks, really helped me on this one
Thanks for the report. If this is affecting everyone, it might be worth opening a PR to add this, however if it’s not going to be a permanent or widespread issue I’d prefer to keep our package.json as aligned as possible with the TryGhost/ghost one (which doesn’t specify an NPM version).
Heroku itself implemented an automatic build workaround for this npm version’s bug.
NPM 5.4.x has introduced a bug, which is blocking the deployment process because Heroku defaults to the latest version of NPM.
This can be fixed by locking NPM 5.3.0 in package.json.
I'm not sure how to do pull requests so I'm just opening an issue so you guys are aware of the issue and how to fix it :-)