Menú
Diagnose and fix "Module not found" errors caused by stale Docker dependency caches. Use when a dependency was added/removed/swapped but the Docker container still has old node_modules.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Opinionated constraints for building better interfaces with agents.
Use when a UI change needs before/after screenshot pairs for a PR or review. Triggers on "vorher/nachher", "before/after screenshots", visual comparison of a frontend refactor, or verifying that a migration did not change the look.
Use when adding or substantially changing a user-facing feature flow that the in-app help guide documents, or when editing the help guide content, screenshots, or PDF export. Triggers on guide-data.ts, /help pages, Hilfe, Anleitung, guide chapters, GuideStep/GuideChapter, or "update the docs/guide".
Use when adding or substantially changing a user-facing feature flow that the in-app help guide documents, or when editing the help guide content, screenshots, or PDF export. Triggers on guide-data.ts, /help pages, Hilfe, Anleitung, guide chapters, GuideStep/GuideChapter, or "update the docs/guide".
Use when discovering a novel solution, pattern, or technique that could benefit the team. Triggers when solving a non-obvious problem, finding a useful workflow, or learning something worth sharing. Also use when user says "make this a skill" or "share this with team".
Use when adding, removing, or renaming environment variables, modifying docker-compose files, or when lefthook flags env sync warnings. Triggers on .env changes, docker-compose edits, or "missing keys" errors.
| name | fix-docker-dependencies |
| description | Diagnose and fix "Module not found" errors caused by stale Docker dependency caches. Use when a dependency was added/removed/swapped but the Docker container still has old node_modules. |
| metadata | {"author":"moto-nrw","version":"1.0.0"} |
Use this when the frontend Docker container throws Module not found: Can't resolve '<package>' but package.json and pnpm-lock.yaml are correct.
Docker caches the pnpm install --frozen-lockfile layer in the dev-deps build stage. When dependencies change in package.json/pnpm-lock.yaml, Docker may reuse a stale cached layer containing old node_modules. This is especially aggressive with BUILDKIT_INLINE_CACHE: 1.
docker compose up --build only checks file hashes — if the lockfile hasn't changed since the last build, Docker reuses the cached install. This fails when switching packages (e.g., better-auth to next-auth).
cd frontend
grep "<package>" package.json
grep "<package>" pnpm-lock.yaml | head -5
Both should return results. If not, run pnpm install first.
ls node_modules/<package>/ 2>&1 | head -5
If missing locally, run pnpm install.
docker compose exec frontend ls node_modules/<package>/ 2>&1 | head -5
If missing inside the container but present locally, the Docker cache is stale.
# 1. Sync local node_modules
cd frontend && pnpm install
# 2. Rebuild Docker without cache
docker compose build --no-cache frontend
# 3. Recreate the container
docker compose up -d frontend
# 4. Verify
docker compose exec frontend ls node_modules/<package>/
# 1. Clean everything locally
cd frontend
rm -rf node_modules .next
pnpm install
# 2. Full Docker reset
cd ..
docker compose down
docker builder prune -f
docker compose build --no-cache frontend
docker compose up -d
# 3. Verify
docker compose exec frontend ls node_modules/<package>/
docker compose up --build reuses cached layers — it does NOT reinstall dependencies.docker compose build --no-cache <service> forces a fresh install.docker compose exec frontend ls node_modules/<pkg>/.After changing dependencies in package.json, always rebuild with --no-cache:
pnpm install && docker compose build --no-cache frontend && docker compose up -d frontend