Docker

Overview

The docker schematic generates a production-ready Dockerfile and a .dockerignore at the specified directory. The Dockerfile is tailored to the package manager you use — selecting the correct base image, lockfile, and install command automatically.

Usage

schematics @nanoforge-dev/schematics:docker

Options

Option	Type	Default	Description
`directory`	`string`	`.`	Destination directory for the generated files
`packageManager`	`"npm" \| "yarn" \| "pnpm" \| "bun"`	`npm`

Generated files

{directory}/
├── Dockerfile
└── .dockerignore

Dockerfile behaviour by package manager

Package manager	Base image	Install command
`npm`	`node:25-slim`	`npm install --no-lockfile`
`yarn`	`node:25-slim`	`yarn install --frozen-lockfile`
`pnpm`	`node:25-slim`	`pnpm install --frozen-lockfile --allow-build=bun`
`bun`	`oven/bun:1.3`	`bun install --frozen-lockfile`

The Dockerfile follows a standard multi-step approach:

Copy package.json and the lockfile.
Install dependencies with frozen lockfile for reproducible builds.
Copy the rest of the source.
Run build.
Start with start.

Examples

Generate a Dockerfile for an npm project:

schematics @nanoforge-dev/schematics:docker

Generate a Dockerfile for a pnpm project:

schematics @nanoforge-dev/schematics:docker --packageManager=pnpm

Generate in a specific directory:

schematics @nanoforge-dev/schematics:docker \
  --packageManager=bun \
  --directory=./my-game

Commands

Configuration

Getting-Started

Schematics

Overview

Usage

Options

Generated files

Dockerfile behaviour by package manager

Examples

​Overview

​Usage

​Options

​Generated files

​Dockerfile behaviour by package manager

​Examples

Overview

Usage

Options

Generated files

Dockerfile behaviour by package manager

Examples