# How to Verify the AI Website Cloner Template Builds Successfully After Cloning > Verify your AI website cloner template builds successfully after cloning. Run npm install and npm run build to compile your project without errors. - Repository: [JCodesMore/ai-website-cloner-template](https://github.com/JCodesMore/ai-website-cloner-template) - Tags: how-to-guide - Published: 2026-07-01 --- **Run `npm install` followed by `npm run build` to execute both the Next.js production build and TypeScript compiler, confirming the project compiles without errors.** After cloning the **JCodesMore/ai-website-cloner-template** repository, you must verify that the Next.js application and TypeScript types compile correctly before development or deployment. This verification process ensures that all dependencies are properly resolved and that the source code meets the strict type-checking standards defined in the project configuration. ## Install Dependencies First Before running any build commands, install the project dependencies listed in **[`package.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/package.json)**. This step downloads all required packages including Next.js, React, TypeScript, and the shadcn/ui components. ```bash git clone https://github.com/JCodesMore/ai-website-cloner-template.git cd ai-website-cloner-template npm install ``` ## Run the Production Build The primary method to verify the project builds successfully after cloning is the **`npm run build`** command. According to the **[`package.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/package.json)** configuration, this script executes `next build && tsc`, which performs two critical validation steps sequentially. ```bash npm run build ``` This command first runs **Next.js** (`next build`) to generate optimized server-side rendered (SSR) and static assets, then immediately runs the **TypeScript compiler** (`tsc`) to validate type safety across the entire codebase. If both steps complete without errors, you will see output confirming the build succeeded and TypeScript compiled successfully. ## Verify Types Without Building If you need to check type correctness without generating the production bundle, use the dedicated TypeScript script. In **[`package.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/package.json)**, the `tsc` script is defined as `tsc --noEmit`, which aligns with the `"noEmit": true` setting in **[`tsconfig.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/tsconfig.json)**. ```bash npm run tsc ``` This performs a strict type-check across all files in `src/app/`, `src/components/`, and `src/lib/` without emitting JavaScript files, providing rapid feedback on type errors. ## Key Configuration Files Understanding the build process requires examining three critical configuration files: ### package.json Build Scripts The **[`package.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/package.json)** file defines the build pipeline in the `scripts` section. The `build` entry combines `next build && tsc` to ensure both the application bundle and TypeScript types are validated during the production build process. ### tsconfig.json Compiler Options The **[`tsconfig.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/tsconfig.json)** file enables strict type-checking with `"strict": true` and `"noEmit": true"`. This configuration ensures that `tsc` only reports errors without generating compiled JavaScript files, as Next.js handles its own compilation internally. ### next.config.js Settings The **[`next.config.js`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/next.config.js)** file contains custom Next.js configuration including image domain settings and experimental flags that affect how `next build` processes the application routes in `src/app/` and components in `src/components/`. ## Troubleshooting Build Failures If either `npm run build` or `npm run tsc` fails, the console output provides specific file paths and line numbers. Common issues include: - **Missing dependencies**: Ensure you ran `npm install` before building - **Type errors in [`src/lib/utils.ts`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/src/lib/utils.ts)**: Verify the `cn()` utility function has correct type annotations - **Next.js configuration errors**: Check **[`next.config.js`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/next.config.js)** for invalid experimental flags Resolve any reported errors and rerun the build command to confirm the project now compiles successfully. ## Summary - **Clone and install**: Run `git clone` followed by `npm install` to prepare the environment - **Full verification**: Execute `npm run build` to validate both Next.js compilation and TypeScript types via the `next build && tsc` pipeline - **Quick type check**: Use `npm run tsc` to run `tsc --noEmit` for fast type validation without generating bundles - **Configuration**: The build relies on **[`package.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/package.json)** scripts, strict settings in **[`tsconfig.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/tsconfig.json)**, and custom rules in **[`next.config.js`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/next.config.js)** - **Success indicator**: Commands completing without console errors confirm the AI Website Cloner Template is ready for development or deployment ## Frequently Asked Questions ### What does `npm run build` actually execute in this project? The `npm run build` command executes the script defined as `next build && tsc` in **[`package.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/package.json)**. This first generates the optimized Next.js production build using `next build`, then runs the TypeScript compiler to verify type safety across the entire codebase, ensuring both the application bundle and type definitions are correct. ### Can I run TypeScript checks without creating a production build? Yes. Run `npm run tsc` to execute `tsc --noEmit` as configured in **[`package.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/package.json)**. This command leverages the `"noEmit": true` setting in **[`tsconfig.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/tsconfig.json)** to check types without generating JavaScript files, providing a faster way to catch type errors without the overhead of the full Next.js build process. ### Why does the build command include both `next build` and `tsc`? The project separates concerns: `next build` handles the actual compilation and bundling of the Next.js application including routes in `src/app/` and components in `src/components/`, while `tsc` performs strict type validation. Combining them ensures that type errors prevent a successful build, maintaining code quality standards enforced by the **[`tsconfig.json`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/tsconfig.json)** strict mode configuration. ### Where are the source files located that get compiled during the build? The source code is organized under the `src/` directory. The **`src/app/`** folder contains the App Router pages and layouts, **`src/components/`** holds the reusable UI components built with shadcn/ui, and **[`src/lib/utils.ts`](https://github.com/JCodesMore/ai-website-cloner-template/blob/main/src/lib/utils.ts)** provides utility functions like `cn()`. All these files are included in the TypeScript and Next.js compilation scope defined by the project configuration.