Say Goodbye to "It Works on My Machine": Why I Built a New Task Runner 🚀

A developer built Lask, an open-source task runner that embeds the execution environment directly into task syntax, using containers to ensure reproducibility across machines. The tool aims to solve the 'It works on my machine' problem by letting developers define environments inline, such as running builds inside a Go 1.22 container or AWS CLI commands in a specific container.

Have you ever spent hours—or even days—debugging a failed build or deployment, only to realize the issue was a slight difference in local environments? Maybe your colleague had Go 1.21 installed instead of Go 1.22. Maybe they were on Windows while you were on a Mac. Or maybe their AWS CLI version was slightly outdated. We've all been there. It's the classic "It works on my machine" problem. To solve this, I built Lask https://github.com/lask-task-runner/lask , a task runner that eliminates environment discrepancies by embedding the execution environment directly into the syntax. Here is why I built it and how it works. 🛑 The limitations of current solutions When trying to standardize tasks, teams usually lean on two approaches: I wanted a tool that combines the reproducibility of CI/CD with the speed and convenience of local execution. ✨ Enter: Lask Lask is an open-source task runner designed around three core principles: Reproducibility, Portability, and Ease of Execution. Instead of relying on whatever tools are installed on your host machine, Lask lets you define the execution environment inline, right next to your command. Here is what a publish task looks like in Lask: // main.lask publish --var: String = "1.0.0" = do { // Run inside a Go 1.22 container $ golang:1.22 GOOS=linux GOARCH=arm64 go build -o bootstrap ./cmd/lambda // Run inside a Zip container $ zip:latest zip function.zip bootstrap // Run inside an AWS CLI container $ aws-cli:2.36 aws lambda update-function-code \ --function-name my-function \ --zip-file fileb://function.zip } By simply typing lask run publish in your terminal, Lask uses containers under the hood to execute each step in its exact required environment. Why this changes the game: bash $ lask repl lask $ rancher/cowsay cowsay "Hello, Lask " 🤝 I'd love your feedback Lask is completely open-source and actively being developed. If you are tired of debugging local environment issues, I would be thrilled if you gave it a try or checked out the code. ⭐ GitHub: lask-task-runner/lask https://github.com/lask-task-runner/lask What tools do you currently use to keep dev environments in sync across your team? Let me know in the comments below 👇