I had this same issue today, and in my case it was heroku deploying in node 14.x environment, which caused an issue with the "pg" module. Specifying node 12.x in my package.json fixed the issue.
1.4m articles
1.4m replys
5 comments
57.0k users