Dev Setup Bootstrap: One-Command Setup and Devcontainers

I ran the stack detector on the bundled demo repository (a Node.js project managed with pnpm, plus Python dependencies in requirements.txt) and generated the files from what it found.

Stack detection

Other files: env_example, compose, pre_commit

Could not decide

• Python version is not pinned (no usable .python-version or .tool-versions entry)

setup.sh

#!/usr/bin/env bash

# One-command project setup. Generated from the files in this repository; review before running.
# Safe to run more than once. It does not install language runtimes itself: it tells you what is
# missing. A package manager can still fetch one when the project asks for it; the report lists those cases.
set -euo pipefail
here="$(dirname "$0")" && [ -n "$here" ] && cd "$here" || exit 1

missing=0
need() { if ! command -v "$1" >/dev/null 2>&1; then echo "missing: $1 ($2)" >&2; missing=1; fi; }
need node 'install Node.js 20.11.1 with your version manager (nvm, fnm, asdf or mise) or from nodejs.org'
need pnpm 'install pnpm: corepack enable works on Node.js before 25, otherwise use your package manager'
need python3 'install Python with your version manager (pyenv, asdf, mise or uv) or from python.org'
if [ "$missing" -ne 0 ]; then echo "Install the tools above, then run this script again." >&2; exit 1; fi

if [ "$(node -p 'process.versions.node.split(".")[0]')" != 20 ]; then echo "warning: this project expects Node 20" >&2; fi
echo '==> node dependencies'
pnpm install --frozen-lockfile
echo '==> python dependencies'
[ -d .venv ] || python3 -m venv .venv
.venv/bin/python -m pip install -r requirements.txt
if [ ! -e .env ] && [ ! -L .env ] && [ ! -L .env.example ]; then cp -- .env.example .env; echo 'created .env from .env.example: fill in the values'; fi
if [ -e .git ] && command -v pre-commit >/dev/null 2>&1; then pre-commit install; else echo 'tip: run pre-commit install inside a git checkout to enable the hooks' >&2; fi

echo 'Setup complete.'

Makefile

# Generated by dev-setup-bootstrap. Recipes are indented with a tab.
.PHONY: setup test lint dev build

setup:
	bash setup.sh

test:
	pnpm test
	.venv/bin/python -m pytest

lint:
	pnpm run lint

dev:
	pnpm run dev

build:
	pnpm run build

.devcontainer/devcontainer.json

{
  "name": "dev",
  "image": "mcr.microsoft.com/devcontainers/base:ubuntu24.04",
  "features": {
    "ghcr.io/devcontainers/features/node:2": {
      "version": "20.11.1"
    },
    "ghcr.io/devcontainers/features/python:1": {}
  },
  "postCreateCommand": "bash setup.sh"
}

Why each line is there

pnpm because of pnpm-lock.yaml and the packageManager field (pnpm@9.12.0), installed with --frozen-lockfile.

• Node.js 20.11.1 from .nvmrc, used both in the version check and in the devcontainer feature.

Python is left unpinned: the repository has no .python-version or .tool-versions entry, so the report lists it under "Could not decide" instead of guessing.

compose.yml was found, but services are not started by setup.sh; the report tells you to start them with your compose command.

Want me to run the same on your repository? Existing files such as a Makefile are never overwritten; you get a merge proposal instead.