-
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
NPM Buildpack should only run "npm install" #109
Comments
joshzarrabi
added a commit
to paketo-buildpacks/nodejs
that referenced
this issue
Sep 10, 2020
This npm-install does not set a launch process. See paketo-buildpacks/npm-install#109 Co-authored-by: Arjun Sreedharan <asreedharan@vmware.com>
Due to RFC 0002, tini has been removed from the group. See paketo-buildpacks/nodejs#241 |
arjun024
added a commit
to paketo-buildpacks/nodejs
that referenced
this issue
Sep 14, 2020
This npm-install does not set a launch process. See paketo-buildpacks/npm-install#109 Co-authored-by: Arjun Sreedharan <asreedharan@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per the Node.js re-architecture RFC, once paketo-buildpacks/nodejs#212 is implemented, we should rename this buildpack to Paketo NPM Install Buildpack and update the buildpack to only run
npm install
. After this is complete, Language family ordering will look like:The text was updated successfully, but these errors were encountered: