-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
package-lock.json
should not be required
#6
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/163493331 The labels on this github issue will be updated when the story is started. |
@scothis Is this blocking you on anything at the moment? The issue certainly makes sense. We're in active development of this cnb and will be supporting more workflows as time goes on. |
Not urgent as I was able to work around the issue by adding a package-lock.json. |
Thanks for this issue @scothis! This has since been fixed and should be released! |
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
?packs v0.0.9
What version of the buildpack you are using?
5c4c6ec
If you were attempting to accomplish a task, what was it you were attempting to do?
Build a project with a package.json file but no package-lock.json.
Many projects will not have a package-lock.json as it's not required by npm, even though it is encouraged. If a project contains an npm-shrinkwrap.json file, the package-lock.json is completely ignored. Many npm alternatives will not generate a package-lock.json file.
What did you expect to happen?
The buildpack should detect and run
npm install
at build time.What was the actual behavior?
The buildpack detects, but errors at buildtime.
Can you provide a sample app?
https://github.com/projectriff-samples/node-square/tree/10ee582a990eab43772f7d99d715740ddcee2b1b
Use
projectriff/builder:0.2.0-snapshot-ci-f2315fde2cae
as the builder image.Please confirm where necessary:
The text was updated successfully, but these errors were encountered: