Out of the box, in the absence of a Procfile, Heroku will run your build script at build time (when you deploy) and your start script as a web dyno at runtime (when your dyno starts).

Your build and start scripts make sense, the former running tsc to compile your TypeScript to JavaScript and the latter running the compiled JavaScript.

Since you want to run a worker process instead of a web process you need a Procfile, but this one hands the work off to the wrong script, using dev instead of start:

worker: npm run dev

Your dev script tries to build your already built application at runtime, which is a problem for a few reasons:

• the immediate issue is that run-s is not available, probably because it was declared as a dev dependency
• building here is redundant since your application was already compiled during deployment,
• if it works at all, it's going to significantly delay startup every time your dyno restarts, you scale your application, etc.,
• like run-s, tsc probably isn't available at runtime (and shouldn't be) because it was declared as a dev dependency

Use your start script instead of your dev script:

worker: npm run start