I've been tempted for a long time to make mise natively capable of running package.json tasks, e.g: `mise run test`. My hesitation is I don't want it to be capable of really any other task definition and users will expect that.

@jdxcode I’ve been pondering this lately - I’ve got a “monorepo” that’s a mix of TypeScript, Ruby, Terraform, etc. (it’s a Rails app…). Mise/Pitchfork would be great for a unified interface for dev environments, but I’m still tinkering with the best way to handle it…

@davidlormor Yeah, I think plugins may be the right answer here. mise can provide the task layer, while a Rails/Pitchfork plugin could auto-define the obvious project tasks instead of making every app hand-write the same glue.