Skip to content
This repository was archived by the owner on Oct 16, 2024. It is now read-only.
This repository was archived by the owner on Oct 16, 2024. It is now read-only.

Confusing messaging around npm start script #44

@joshwlewis

Description

@joshwlewis

I have a package.json that looks like this:

{
  "main": "dst/index.js",
  "scripts": {
    "start": "node dst/index.js",
    "compile": "tsc -p .",
    "test": "jest"
  },
  // ...other stuff
}

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions