Every project starts with npm install and a dev server. You don't need to master every tool, but you need to understand what they do so you can fix things when they break, and so you are not lost when a team uses pnpm instead of npm.
package.json, dependencies vs devDependencies, semver ranges, lockfiles, scripts, and npx. The concepts are the same in every package manager.
What a bundler does (modules, transpiling, minifying, code splitting) and how Vite gives you a fast dev server. Vite 8 now uses the Rust-based Rolldown bundler.
ESLint catches bugs, Prettier ends style debates, and Biome does both in one fast tool.
Installing Node with a version manager, what the runtime does, and running scripts. Bun and Deno are alternatives worth knowing about.
Ships with Node. Every tutorial uses it. Perfect for learning.
Faster installs, saves disk space, strict about dependencies, great for monorepos. Very common in professional teams.
Still used in many existing codebases. Learn it when a job needs it.
Very fast runtime plus package manager. Good for side projects; check team support first.
Our takeLearn with npm, move to pnpm for real projects. They share the same concepts, so switching takes an afternoon. The command you use matters far less than understanding lockfiles and semver.
The industry standard with the biggest plugin ecosystem. You will meet it in most jobs.
One tool, very fast, almost zero config. Great for new projects.
Our takeKnow ESLint and Prettier because you will meet them at work. Biome is a fine choice for your own new projects.
You can set up a new project from scratch with Vite, TypeScript, ESLint, and Prettier, and explain every file it creates.
Stage project
Build a reusable starter repository that you will use for every project after this.
Last reviewed · Full roadmap