`heroku local` no longer works for projects without a Procfile

[36degrees]

Since the release of Heroku 11, heroku local now errors when run against a project that does not include a Procfile:

npx --yes heroku local               
    Error: ENOENT: no such file or directory, open 'Procfile'
    Code: ENOENT

Heroku 10 previously supported this by falling back to npm start:

$ npx --yes heroku@10 local            
 ›   Warning: heroku update available from 10.17.0 to 11.0.1.
[WARN] ENOENT: no such file or directory, open 'Procfile'
[OKAY] package.json file found - trying 'npm start'
[WARN] ENOENT: no such file or directory, open 'Procfile'
[OKAY] package.json file found - trying 'npm start'
# Project runs – output omitted

This might be an unintentional feature as it looks like the logic for it is coming from foreman. It'd be good to understand if it's an intentional change, and whether restoring the previous behaviour is an option.

[heroku-johnny]

@36degrees thank you for reporting this. We will investigate the issue and report back as soon as possible

[k80bowman]

@36degrees a fix for this was published in v11.2.0 of the CLI. We've added a --start-cmd flag you can use to specify a command to run when you aren't using a procfile. I'm going to go ahead and close this issue, but if this continues to be a problem for you, please re-open this issue or open a new one. Thank you!