Closed ghost closed 3 years ago
Looks like this upgrade of paketo-buildpacks/nodejs
is failing because of this change to the detection criteria in paketo-buildpacks/node-start
. Previously if there was any *.js
file in the application directory the nodejs buildpack would detect. Now it looks for specific files, which aren't present when build a riff node function.
The node-start
buildpack exists to provide a start command and that command is overwritten by the projectriff/node-function-buildpack
anyways. However, node-start
is a required component of the paketo-buidpacks/nodejs
buildpacks. Perhaps we want to move away from using the composite nodejs
buildpack and instead compose a custom group like we do for java functions?
Another option would be to see if node-start
can become optional in the nodejs buildpack.
Bumps
gcr.io/paketo-buildpacks/nodejs
from0.0.10
to0.1.2
.