Tutorials covering the tools that developers use every day — version control, editors, build systems, package managers, containers, and the command-line utilities that make work faster. Each chapter is standalone, built around real examples and verified commands.
A Docker image built without a strategy becomes an archaeological record of everything that went into producing it. The compiler, the development dependencies, the source code, the package manager caches—all of it remains in the final artifact, even though the running container needs none of it. A straightforward Node.js or Java build easily reaches 1.2…
Testing a package locally before publishing it is not a single workflow. npm link and npm pack solve different problems, and the choice between them determines whether the test reflects the published artifact or a symlinked approximation of it. Key point: npm link creates a symlink, which means the consumer project sees your working directory…
A compiled binary is a promise. It says: everything this program needs is inside this file. No interpreter, no package manager, no shared library. Just instructions the kernel can execute directly. Go and Rust make this promise readily—with the right build flags. Node.js can approximate it with newer tooling that embeds the runtime. Docker’s multi-stage…
npm’s configuration system is a layered hierarchy of files, environment variables, and command-line flags. The .npmrc file is the persistent layer: an INI-formatted list of key = value pairs that npm reads at startup. The file exists at four scopes—project, user, global, and builtin—and the values resolve in priority order, with the most specific scope…
The base image is the first decision in any Dockerfile, and it is the one that is hardest to reverse. It determines the C library, the package manager, the shell, the attack surface, and the fundamental compatibility of everything that follows. A choice made casually in a FROM line ripples through every build, every scan,…
A scoped package is a package whose name is prefixed with a namespace, written as @scope/package-name. The scope is the part between the @ and the /, and it groups related packages under a single namespace. Scopes exist to prevent name collisions: a package named utils is unique, but @myorg/utils and @otherorg/utils can coexist because…
A Docker build is a script that runs with whatever privileges the builder has. Historically, that script had no safe way to use credentials. Build arguments (–build-arg) are visible in the image history and docker history output. Environment variables (ENV) end up in the image configuration. Copying a credential file into the build context and…
An npm workspace is a repository whose root package.json contains a workspaces field listing the directories that hold other package.json files. Running npm install at the root installs every workspace’s dependencies in one pass and symlinks the local packages into the root node_modules, so they can depend on each other without being published to a…
A Docker build that reinstalls every dependency on every run is a build that wastes time. Package managers download from the network, unpack archives, and write to disk—work that is identical across builds unless the dependency files change. Layer caching helps only when the instruction sequence and inputs are unchanged. The moment you touch a…
Security in npm operates on two axes: the dependency tree and the credentials that authorize publishing. The dependency tree is audited with npm audit, which compares installed packages against a vulnerability database and offers automated fixes. The credentials are managed as access tokens, which have been consolidated into a single granular model as of November…