Preparing your workspace
Project configuration controls tool behavior, while environment-specific values allow the same codebase to run in different environments.
Real projects use configuration files for tools such as TypeScript, ESLint, Prettier, testing frameworks, bundlers, and application frameworks. Environment variables provide values that change between local, test, and production environments. Developers also use formatting and linting tools to enforce consistent code quality. The goal is not to memorize every configuration file, but to understand that tools are configurable and that configuration should be explicit, predictable, and safe.
A Next.js project may use an environment file for a public API URL, TypeScript configuration for type checking, ESLint for code rules, and Prettier for formatting.
.env.local
API_URL=http://localhost:4000
package.json
{
"scripts": {
"lint": "eslint .",
"format": "prettier --write ."
}
}Project configuration and environment values control tooling and application behavior without hardcoding everything into source files.