[V5] How do I resolve this Heroku deployment error?

[KungWaz]

When deploying to Heroku using
git push heroku main
I get this error:

$ git push heroku main
Enumerating objects: 98, done.
Counting objects: 100% (98/98), done.
Delta compression using up to 8 threads
Compressing objects: 100% (84/84), done.
Writing objects: 100% (98/98), 148.58 KiB | 3.91 MiB/s, done.
Total 98 (delta 9), reused 3 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Building on the Heroku-20 stack
remote: -----> Node.js app detected
remote:
remote: -----> Creating runtime environment
remote:
remote:        NPM_CONFIG_LOGLEVEL=error
remote:        NODE_VERBOSE=false
remote:        NODE_ENV=production
remote:        NODE_MODULES_CACHE=true
remote:
remote: -----> Installing binaries
remote:        engines.node (package.json):  unspecified
remote:        engines.npm (package.json):   unspecified (use default)
remote:
remote:        Resolving node version 12.x...
remote:        Downloading and installing node 12.20.1...
remote:        Using default npm version: 6.14.10
remote:
remote: -----> Installing dependencies
remote:        Installing node modules
remote:        npm ERR! Error while executing:
remote:        npm ERR! /usr/bin/git ls-remote -h -t ssh://[email protected]/thetutlage/matchit.git
remote:        npm ERR!
remote:        npm ERR! Host key verification failed.
remote:        npm ERR! fatal: Could not read from remote repository.
remote:        npm ERR!
remote:        npm ERR! Please make sure you have the correct access rights
remote:        npm ERR! and the repository exists.
remote:        npm ERR!
remote:        npm ERR! exited with error code: 128
remote:
remote:        npm ERR! A complete log of this run can be found in:
remote:        npm ERR!     /tmp/npmcache.pwl7i/_logs/2021-01-31T11_11_39_517Z-debug.log
remote:
remote: -----> Build failed
remote:
remote:        We're sorry this build is failing! You can troubleshoot common issues here:
remote:        https://devcenter.heroku.com/articles/troubleshooting-node-deploys
remote:
remote:        Some possible problems:
remote:
remote:        - Node version not specified in package.json
remote:          https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
remote:
remote:        Love,
remote:        Heroku
remote:
remote:  !     Push rejected, failed to compile Node.js app.
remote:
remote:  !     Push failed
remote:  !
remote:  ! ## Warning - The same version of this code has already been built: c04c124655dd388fe7141a5e84498731f78ec6e3
remote:  !
remote:  ! We have detected that you have triggered a build from source code with version c04c124655dd388fe7141a5e84498731f78ec6e3
remote:  ! at least twice. One common cause of this behavior is attempting to deploy code from a different branch.
remote:  !
remote:  ! If you are developing on a branch and deploying via git you must run:
remote:  !
remote:  !     git push heroku <branchname>:main
remote:  !
remote:  ! This article goes into details on the behavior:
remote:  !   https://devcenter.heroku.com/articles/duplicate-build-version
remote:
remote: Verifying deploy...

I have tried to follow the steps in the Heroku docs as well as this previous discussion: link

This is my package.json

{
  "name": "myapp",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "build": "node ace build --production",
    "start": "ENV_SILENT=true node build/server.js",
    "dev": "node ace serve --watch"
  },
  "devDependencies": {
    "@adonisjs/assembler": "^3.0.6",
    "adonis-preset-ts": "^1.1.0",
    "pino-pretty": "^4.3.0",
    "typescript": "^4.1.3",
    "youch": "^2.1.1",
    "youch-terminal": "^1.0.1"
  },
  "dependencies": {
    "@adonisjs/auth": "^5.1.1",
    "@adonisjs/core": "^5.0.4-preview-rc",
    "@adonisjs/lucid": "^10.0.0",
    "@adonisjs/mail": "^5.2.3",
    "@adonisjs/repl": "^1.1.6",
    "@adonisjs/session": "^4.0.6",
    "@adonisjs/view": "^3.1.0",
    "crypto-random-string": "^3.3.0",
    "luxon": "^1.25.0",
    "mysql": "^2.18.1",
    "phc-argon2": "^1.0.11",
    "proxy-addr": "^2.0.6",
    "reflect-metadata": "^0.1.13",
    "source-map-support": "^0.5.19"
  }
}

And this is my Procfile

release: ENV_SILENT=true node ace migration:run --force
web: ENV_SILENT=true npm start

EDIT
I have now created a basic AdonisJS api app, just did the init and added the Procfile, I get the same error, so it seems it is a general issue.

[McSneaky]

Do you have git installed on the system?

[KungWaz]

I just followed this guide in combination with the documentation on Heroku. I would assume that Heroku has git installed since I push the code to them. Or am I missing something here?

[thetutlage]

Tried deploying an app on Heroku on node 12 (their default version) and all went fine. If you are using a custom Procfile or heroku.yml file, then do share that with us

[KungWaz]

The Procfile I have already shared, in the bottom of my post. I do not have any heroku.yml file from what I can see. Did you specifiy the node version in the package.json?

From what I can see in the logs I have shared it looks like node v12?

...
Resolving node version 12.x...
remote:        Downloading and installing node 12.20.1...
remote:        Using default npm version: 6.14.10
...

[KungWaz]

@thetutlage any idea what I might be doing wrong/differntly from you?

[Litchstarken]

check the node version

[avidcoder123]

I had the same problem, try deleting package-lock.json. If that doesn't work clear your build cache. There's currently a dependency error in package-lock.json that should be fixed soon.

[KungWaz]

Ok, I will try that, should I .gitignore it or just delete and re-install or delete it and commit?

[avidcoder123]

Delete it and commit. The heroku buildpack will automatically regenerate it with the correct packages.

[moinabyssinia]

deleting package-lock.json solved the problem for me - thanks!

[Angel-Arceo]

thanks, man!

[ruan-azevedo]

I had this problem today and I realized that I was using node v15 on my local env and Heroku was deploying the app on Node 16.

Just specified the node version on package.json and the deploy is working fine now:

"engines": {
    "node": "15.x"
},