# Build Scripts in the gods-eye-view Project: A Complete Guide > Discover build scripts in the gods-eye-view project. Learn how Vite powers the build process and find auxiliary scripts for enhanced development. - Repository: [Bilawal Sidhu/gods-eye-view](https://github.com/bilawalsidhu/gods-eye-view) - Tags: how-to-guide - Published: 2026-08-30 --- **The gods-eye-view repository uses Vite as its primary build tool, with the main build script defined in [`package.json`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/package.json) as `"build": "vite build"` and auxiliary utilities located in the `scripts/` directory.** The gods-eye-view project by bilawalsidhu relies on a modern Vite-based build pipeline. Understanding how these build scripts work is essential for contributing to the codebase or deploying the application. This guide breaks down the core build configuration and auxiliary scripts that power the development workflow. ## Core Build Configuration The build process centers on two key files that define how the application is bundled and optimized for production. ### package.json Scripts In [`package.json`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/package.json), the build command is explicitly defined under the `scripts` section. The `"build"` key maps to `"vite build"`, which invokes the Vite bundler with production settings. This standardizes the build process across different environments and ensures consistent output generation. ### vite.config.js The Vite configuration stored in [`vite.config.js`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/vite.config.js) controls bundling behavior, output directories, and optimization settings. This file determines how assets are processed and how the final distribution bundle is structured according to the gods-eye-view project requirements. ## Running the Build To execute the production build or start development, use the following npm commands: ```bash # Install dependencies npm ci # Start the development server for live preview npm run dev # Execute the production build npm run build # Preview the built application locally before deploying npm run preview ``` The `npm run build` command triggers Vite to compile the source code into optimized static assets ready for deployment. The `preview` command serves these built files locally to verify the production output. ## Auxiliary Scripts in the scripts/ Directory Beyond the core Vite pipeline, the `scripts/` directory contains helper utilities that support development and testing workflows. These scripts are invoked manually rather than being part of the automated build process. ### Available Utility Scripts - **`run-unit-tests.mjs`**: Executes the project's test suite to validate code functionality before deployment. - **[`opensky-import-client.sh`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/opensky-import-client.sh)**: Handles data import operations from external sources, supporting the application's data layer. To run these auxiliary scripts directly: ```bash # Execute the test suite node scripts/run-unit-tests.mjs # Run the data import utility (requires appropriate permissions) bash scripts/opensky-import-client.sh ``` These utilities complement the main build process but do not execute automatically during `vite build`. They provide specialized functionality for testing and data management within the gods-eye-view ecosystem. ## Development vs Production Workflows Understanding the distinction between development and production commands ensures efficient workflow optimization. The **`dev`** script starts a hot-reload development server with minimal bundling for fast iteration, while **`build`** performs aggressive optimization including minification, tree-shaking, and asset compression for deployment. When preparing a release, always run `npm run build` followed by `npm run preview` to validate the production bundle locally. This prevents deployment issues by catching configuration errors or missing assets before they reach production environments. ## Summary - The primary build command is `npm run build`, which executes `vite build` as defined in [`package.json`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/package.json). - Vite configuration is managed in [`vite.config.js`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/vite.config.js) and controls the bundling pipeline. - Auxiliary scripts in the `scripts/` directory include `run-unit-tests.mjs` for testing and [`opensky-import-client.sh`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/opensky-import-client.sh) for data imports. - Use `npm run preview` to serve the production build locally for verification before deployment. ## Frequently Asked Questions ### What is the main build command for gods-eye-view? The main build command is `npm run build`. This invokes the Vite bundler via the script definition in [`package.json`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/package.json), producing optimized static assets in the distribution folder. ### Where is the Vite configuration located? The Vite configuration is stored in [`vite.config.js`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/vite.config.js) at the repository root. This file controls bundling settings, output paths, and optimization parameters for both development and production builds. ### What auxiliary scripts are available in the scripts/ directory? The `scripts/` directory contains `run-unit-tests.mjs` for executing the test suite and [`opensky-import-client.sh`](https://github.com/bilawalsidhu/gods-eye-view/blob/main/opensky-import-client.sh) for external data imports. These support development workflows but run independently of the core Vite build process. ### How do I preview the production build locally? Run `npm run preview` after executing `npm run build`. This command starts a local server using the generated production files, allowing you to verify the optimized output before deployment.