Hi @ankit1029,
I followed the instructions you mentionned and faced the same issue as you.
It seems to be an issue from a package of puppeeter as mentionned in the thread here : https://github.com/puppeteer/puppeteer/issues/2746.
But as far as I know this kind of issues (caused generally because a catch() is missing in a promise chain, it isn’t a blocking error. On my side, it could pursue the script until the end actually.
But I remember that nodejs has been notifying for awhile that an unhandled rejection may become abort the script in the future, it is maybe true today.
Which npm version do you have ?