`npm start` fails with "Error: 'probot-run' does not exist"

Bug Report

Current Behavior

I’m new to Probot and I’d like to dig into it a little (like adding simple information to startup logs as Probot version). Anyway, I’m checking out current master branch (but I tested this with other refs, like v10.0.1 for example, same behavior), and after clone + npm install, I try to run npm start but it throws an exception:

> probot@0.0.0-development start /Users/alex/git/probot
> node ./bin/probot run

/Users/alex/git/probot/node_modules/commander/index.js:832
        throw new Error(executableMissing);
        ^

Error: 'probot-run' does not exist
 - if 'run' is not meant to be an executable command, remove description parameter from '.command()' and use '.description()' instead
 - if the default executable name is not suitable, use the executableFile option to supply a custom name
    at ChildProcess.<anonymous> (/Users/alex/git/probot/node_modules/commander/index.js:832:15)
    at ChildProcess.emit (events.js:314:20)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:274:12)
    at onErrorNT (internal/child_process.js:468:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)

Expected behavior/code

I’m not sure if this is the correct way to start up Probot in development mode but I couldn’t find any piece of docs suggesting otherwise.

Environment

• Probot version(s): commit e3f6cf583b63805e76958bb43a1e7694b15b8524
• Node/npm version: v14.8.0
• OS: macOS v10.15.6

[gr2m]

Let me close the issue as the original problem is resolved. Please feel free to open new ones as needed

[shaftoe]

All right, it makes all sense, thanks for the clarification!