What's your approach to cross platform tasks?

[airtonix]

So this is a question for teams that (righly or wrongly) decide that they don't want to force their windows teams members to just install wsl2 and develop there with vscode remote.

What approach do you declare for your mise task files so that they run with same effect on windows powershell as they do on linux bash?

1. do you avoid the shell difference by adding powershell to mise tools and all your tasks use powershell?
2. do you force your windows team mates to use wsl2?
3. do you do some kind of branching in your task files based on OS ?

[airtonix]

Would be it be beneficial for Mise itself to automatically choose the appropriate task file based on os and shell available?

.mise/tasks/build # contains #!/bin/bash
.mise/tasks/build__windows is a ps1 file

or

.mise/tasks/build
.mise/tasks/build__darwin # contains #!/bin/bash
.mise/tasks/build__linux # contains #!/bin/bash

or

.mise/tasks/build.ps1
.mise/tasks/build__darwin.zsh
.mise/tasks/build__linux.pwsh
.mise/tasks/build__linux.bash

Main benefits for some kind of task file resolution based on current shell and os would probably be most applicable to opensource projects seeking to greatly reduce friction while trying to provision development environment.

I typically create a .mise/tasks/setup task so my project setup steps can be

1. clone the repo
2. install mise
3. mise run setup

It'd be great if I could provide different files so that different platforms can get setup faster.

[IIIMADDINIII]

I tried to solve it by not using shell scripts in the past. Basically i used nodejs to create my scripts which now can run on most platforms. together with execa it not as bad as it seams.

Now with mise i have the problem that i can not execute file based targets in a cross platform manner without also defining a task in mise.toml