Taking a look at the dates in the changelog for the node buildpack on heroku, I’d guess that this the fix for this issue is in the most recent buildpack, so you might try v22 instead, to see if that works.
we support a couple of different builders, so you might have more success using a Dockerfile. There’s some good discussion in the following thread: