Build

Browsers can't directly understand everything you write during development, like TypeScript, JSX, Vue files, and Tailwind class names. A build is like turning raw ingredients into ready-to-heat meals: it translates everything into plain JavaScript and CSS, strips spaces and comments to shrink the size, bundles lots of files into a few, and outputs them to a folder like dist, build, or .next.

Common build tools are Vite and Webpack. Frameworks usually have them set up already, so you just run npm run build.

If the dev server runs, that doesn't mean the build will succeed. Type checks and linting are stricter during the build, and it's very common for things to work fine locally and then fail to build right before launch. It's a good idea to run a build every time the AI finishes a batch of features, so you catch problems early.