Buildpack failing instantly, suddenly?

[ckcollab]

-----> Node.js app detected
/app/tmp/buildpacks/.../bin/compile: line 26: 
/app/tmp/buildpacks/.../etc/vendor/stdlib_v7.sh: No such file or directory
 !     Push rejected, failed to compile Node.js app.
 !     Push failed

Getting this instantly on builds now, across multiple apps (don't think error is on my end)

[AugustMiller]

Just came to report the same thing—odd, granted the file still exists in the build pack, at this location!

We're blocked on deployments until this is resolved, although… there's an alternative syntax for specifying a version with a hash: https://devcenter.heroku.com/articles/buildpacks#buildpack-references

I'll post another comment if I can get this working. ✌️

[billyburgoa]

I am getting the same messages.

-----> Node.js app detected

/app/tmp/buildpacks/a104ebb80184ba556a3457859a381585c1c182694d8086bfcdabe39f3fe5857835812b209be5647b385deaddf7afa081b0f0c5d9d1683b767fb8abc0c3b79cc0/bin/compile: line 26: /app/tmp/buildpacks/a104ebb80184ba556a3457859a381585c1c182694d8086bfcdabe39f3fe5857835812b209be5647b385deaddf7afa081b0f0c5d9d1683b767fb8abc0c3b79cc0/etc/vendor/stdlib_v7.sh: No such file or directory

 !     Push rejected, failed to compile Node.js app.

 !     Push failed

[ozeas]

Same thing.

-----> Node.js app detected
/app/tmp/buildpacks/a104ebb80184ba556a3457859a381585c1c182694d8086bfcdabe39f3fe585783
5812b209be5647b385deaddf7afa081b0f0c5d9d1683b767fb8abc0c3b79cc0/bin/compile: line 26: 
/app/tmp/buildpacks/a104ebb80184ba556a3457859a381585c1c182694d8086bfcdabe39f3fe585783
5812b209be5647b385deaddf7afa081b0f0c5d9d1683b767fb8abc0c3b79cc0/etc/vendor/stdlib_v7.sh:
 No such file or directory

 !     Push rejected, failed to compile Node.js app.
 !     Push failed

[AugustMiller]

Temporary Fix to roll back to v167 release:

$ heroku buildpacks:set 'https://github.com/heroku/heroku-buildpack-nodejs#v167' --app your-app-name

(I am not a maintainer, and not sure if this is the recommended route, but it's gotten our app back online!)

[billyburgoa]

Temporary Fix to roll back to v167 release:

$ heroku buildpacks:set 'https://github.com/heroku/heroku-buildpack-nodejs#v167' --app your-app-name

(I am not an author, and not sure if this is the recommended route, but it's gotten our app back online!)

I don't know which version of my app is running in heroku. The mine is still running, though.

[danielleadams]

I rolled back the buildpack, so this should be working again. The buildpack is using v167 by default now.

[ozeas]

Temporary Fix to roll back to v167 release:

$ heroku buildpacks:set 'https://github.com/heroku/heroku-buildpack-nodejs#v167' --app your-app-name

(I am not an author, and not sure if this is the recommended route, but it's gotten our app back online!)

it worked for me too.

[billyburgoa]

Things seem to be working fine again. I just deployed the branch and it got compiled without any issues.

[danielleadams]

Going to close this since I rolled back. Please see my previous comment: #749 (comment)

[AugustMiller]

Thanks for the quick response! 💓