You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2024. It is now read-only.
And I see this messaging when building the project with this buildpack:
[builder] ---> Parsing package.json
[builder] ---> No file to start server
[builder] ---> either use 'docker run' to start container or add index.js or server.js
This messaging makes it sound like I'm doing something wrong and I spent a few cycles trying to understand if I should fix my project layout. In the end, everything worked as-is, and the nodejs-npm-buildpack seemed to know about the start script. I just wonder if this message makes sense for a repo where there is no index.js/server.js but the start script is defined.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a package.json that looks like this:
And I see this messaging when building the project with this buildpack:
This messaging makes it sound like I'm doing something wrong and I spent a few cycles trying to understand if I should fix my project layout. In the end, everything worked as-is, and the
nodejs-npm-buildpack
seemed to know about the start script. I just wonder if this message makes sense for a repo where there is no index.js/server.js but the start script is defined.The text was updated successfully, but these errors were encountered: