No. It wasn't meant for OP (is-promise) because that would require tests for the imports. I saw some work around changing versions in the package.json and lock

No. It wasn't meant for OP (is-promise) because that would require tests for the imports. I saw some work around changing versions in the package.json and lockfiles in the github issue. Instead of that, you could just roll back to the previous commit. Way easier. The package author also changed the earlier version after fixing it. It would stop your shit from failing at least.