Configuration Files
Relevant source files
The following files were used as context for generating this wiki page:
Configuration files in the AVP Demo project establish the foundational environment for a modern Next.js 16 application. These files define the build pipeline, TypeScript compiler constraints, dependency management, and global styling rules that govern the entire repository.
The configuration architecture is designed for a React 19 environment, utilizing the Next.js App Router and Tailwind CSS 4 for styling. This ensures high performance, type safety through strict TypeScript rules, and a streamlined development workflow.
Project Metadata and Dependencies
The project's lifecycle and external requirements are defined in package.json. It specifies the runtime environment and the specific versions of frameworks used to build the application.
Key Scripts and Dependencies
The project utilizes standard Next.js scripts for development, building, and linting.
| Script | Command | Purpose |
|---|---|---|
dev | next dev | Starts the development server with Hot Module Replacement. |
build | next build | Compiles the application for production deployment. |
start | next start | Starts the production server after a build. |
lint | eslint | Runs static analysis to ensure code quality. |
Sources: package.json:6-11
Dependency Overview
The application relies on React 19 and Next.js 16. Key UI enhancements are provided by framer-motion for animations and tailwindcss 4 for utility-first styling.
Sources: package.json:13-26
TypeScript Configuration
The tsconfig.json file configures the TypeScript compiler (tsc) to enforce strict type checking and handle path aliasing. This ensures that the codebase remains maintainable and less prone to runtime errors.
Compiler Settings
The configuration targets ES2017 and uses the bundler module resolution strategy, which is optimized for modern tools like Next.js.
The diagram above illustrates the hierarchy of TypeScript configuration settings applied to the project.
Key parameters include:
- Strict Mode: Enabled to ensure maximum type safety.
- Path Aliasing: The
@/*prefix is mapped to the root directory./*, allowing for cleaner imports like@/components/Navbar. - Incremental: Set to
trueto speed up subsequent builds by reusing information from previous compilations.
Sources: tsconfig.json:2-31
Next.js Build Configuration
The next.config.ts file serves as the primary entry point for customizing the Next.js build process. While currently initialized with default settings, it imports the NextConfig type to provide full IntelliSense and type validation for future optimizations such as image domain whitelisting or environment variable management.
Sources: next.config.ts:1-7
Styling and Theme Configuration
The project uses Tailwind CSS 4, which moves configuration into CSS via the @theme directive. This approach integrates theme variables directly with CSS custom properties.
Global Styles and Theme Variables
The app/globals.css file defines the color palette and typography constraints.
| Variable | Light Mode (Default) | Dark Mode |
|---|---|---|
--background | #ffffff | #0a0a0a |
--foreground | #171717 | #ededed |
Sources: app/globals.css:3-17
Layout Integration
Global configurations are applied at the root through the app/layout.tsx file, which sets the language and base background/text colors for the entire application.
export default function RootLayout({ children }: { children: React.ReactNode }) {
return (
<html lang="en">
<body className="bg-black text-white">
<Navbar />
{children}
<Footer />
<WhatsAppFloat />
</body>
</html>
);
}
Sources: app/layout.tsx:11-19
Summary
The configuration layer of the AVP Demo project is built on a "strict-by-default" philosophy. By leveraging TypeScript's strict mode and Next.js 16's optimized build pipeline, the project establishes a robust foundation for a luxury supercar showcase platform. These files collectively manage the transition from development to a production-ready Europe-wide service.