Make & Task Runners

Overview

Every project needs a way to run common commands (build, test, lint, deploy) without remembering the exact incantation. Make, Just, and Task provide a consistent make build or just test interface regardless of the underlying tech stack.

Tool Comparison

GNU Make

Makefile Anatomy

A Makefile consists of targets, prerequisites, and recipes. Recipes must be indented with a tab (not spaces).

target: prerequisites
	recipe-command

Use .PHONY to declare targets that don't represent files:

.PHONY: build test lint clean dev

Example Makefile

A polyglot project with both Node.js and .NET:

.PHONY: build test lint clean dev

build:
	npm run build
	dotnet build

test:
	npm test
	dotnet test

lint:
	npm run lint
	dotnet format --verify-no-changes

clean:
	rm -rf dist/ bin/ obj/ node_modules/

dev:
	npm run dev

Variables

APP_NAME := myapp
VERSION := 1.0.0

build:
	docker build -t $(APP_NAME):$(VERSION) .

Automatic Variables

Include Other Makefiles

include common.mk

Conditional Logic

ifeq ($(OS),Windows_NT)
	SHELL := powershell.exe
endif

Just

Justfile Syntax

Just is simpler than Make — no tab requirement, first-class arguments, and OS-conditional recipes:

default:
    @just --list

build:
    npm run build
    dotnet build

test *args:
    npm test {{args}}
    dotnet test {{args}}

lint:
    npm run lint
    dotnet format --verify-no-changes

dev port="3000":
    PORT={{port}} npm run dev

# Run in PowerShell on Windows
[windows]
clean:
    Remove-Item -Recurse -Force dist, bin, obj, node_modules

[unix]
clean:
    rm -rf dist/ bin/ obj/ node_modules/

Why Just over Make

• No tab sensitivity — indentation uses spaces, not tabs
• Recipe arguments — just test --verbose passes --verbose to the recipe
• OS-conditional recipes — [windows] and [unix] annotations for cross-platform support
• Dotenv loading — set dotenv-load to automatically load .env files
• Better error messages — clearer feedback when recipes fail

Task (Taskfile)

Taskfile.yml Syntax

version: '3'

tasks:
  build:
    cmds:
      - npm run build
      - dotnet build

  test:
    cmds:
      - npm test
      - dotnet test

  lint:
    cmds:
      - npm run lint
      - dotnet format --verify-no-changes

  dev:
    cmds:
      - npm run dev
    env:
      PORT: 3000

  clean:
    cmds:
      - rm -rf dist/ bin/ obj/ node_modules/

Why Task

• YAML — familiar syntax for anyone working with CI/CD, Kubernetes, or Docker Compose
• Cross-platform — single binary, works on Windows, macOS, and Linux
• Task dependencies — deps: [build] ensures prerequisites run first
• Conditional execution — skip tasks based on file changes or environment
• Dotenv support — automatically loads .env files
• Watch mode — task --watch test re-runs on file changes

When to Use Which

Best Practices

• Put a Makefile, Justfile, or Taskfile in every project root — it serves as the entry point for all commands
• Use it as the single interface for all project operations — build, test, lint, format, deploy, clean
• Document available commands with make help / just --list / task --list so new developers can discover what's available
• Keep recipes simple — delegate to real build tools (npm, dotnet, cargo) rather than encoding complex logic in the task file
• Use task runners for developer experience, not as a replacement for language-specific build systems (Gradle, webpack, MSBuild)
• Commit the task file to version control and document it in the README so the whole team uses the same commands