Closed tmobaird closed 3 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/178138764
The labels on this github issue will be updated when the story is started.
Upstream Node has deprecated the 10.x version line and thus the Ruby buildpack will be removing support for Node 10.x after May 27th, 2021. see issue #239
This is expected behavior at this time as we introduced the 14.x.x version line of Node.js into the Ruby buildpack to allow folks time to ensure apps can build using 14.x.x prior to removing the 10.x.x Node.js version line from the buildpack.
We follow the node LTS schedule found here for future reference on when to expect version lines to be removed: https://nodejs.org/en/about/releases/
Closing the issue for now, but feel free to re-open should you have further concerns!
What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running
cf curl /v2/info && cf version
? cf version 6.50.0+4f0c3a2ce.2020-03-03What version of the buildpack you are using? v1.8.38
If you were attempting to accomplish a task, what was it you were attempting to do? Cf push rails app with webpacker
What did you expect to happen? The app to compile assets successfully (build webpacker succuessfully) and start the app.
What was the actual behavior? The app failed to compile assets and raised this error while doing so:
The app has a package.json with engine
"node": "^10.22.1",
, which should match node 10.24.1 that is included in the buildpack. My assumption is that this is not being honored by the buildpack and is just installing the latest 14.6.1 that is on the buildpack. I'm not sure if this is what is expected. Curious if there is anything like a .node-version file or anything that is honored instead.Also wondering if this is even relevant given (https://github.com/cloudfoundry/ruby-buildpack/issues/239) coming at the end of the month.
Full Stacktrace:
Please confirm where necessary: