# Available Scripts in the open-seo package.json: Complete Reference

> Discover all seven npm scripts in the open-seo package.json. Master local dev, production builds, and type-checking for your open-seo project.

- Repository: [Every App/open-seo](https://github.com/every-app/open-seo)
- Tags: api-reference
- Published: 2026-07-26

---

**The [`package.json`](https://github.com/every-app/open-seo/blob/main/package.json) in the every-app/open-seo repository defines seven npm scripts that manage the development lifecycle, from local dev servers to production builds and type-checking.**

The every-app/open-seo project automates its workflow through npm scripts defined in the root [`package.json`](https://github.com/every-app/open-seo/blob/main/package.json). These scripts provide standardized commands for starting development environments, compiling TypeScript, running tests, and linting code. Understanding these available scripts is essential for anyone contributing to or deploying the open-seo application.

## Core Development Scripts

The development-focused scripts in [`package.json`](https://github.com/every-app/open-seo/blob/main/package.json) handle local server startup and hot-reloading.

### dev

The `dev` script starts the development server with hot-reloading enabled. This is the primary command for local development work.

```bash
npm run dev

```

### start

The `start` script runs the compiled application in production mode. This command is typically used in Docker containers or production servers after a build has been generated.

```bash
npm run start

```

## Build and Type-Checking Scripts

The build pipeline scripts manage TypeScript compilation and production optimization as implemented in every-app/open-seo.

### build

The `build` script generates an optimized production build of the application. This compiles TypeScript and bundles assets for deployment.

```bash
npm run build

```

### type-check

The `type-check` script runs TypeScript type validation without emitting JavaScript files. This uses the configuration defined in [`tsconfig.json`](https://github.com/every-app/open-seo/blob/main/tsconfig.json) to verify type safety across the codebase.

```bash
npm run type-check

```

### prepare

The `prepare` script executes pre-publish steps such as building the project and running type checks. This runs automatically during `npm install` if the package is installed as a dependency.

```bash
npm run prepare

```

## Quality Assurance Scripts

These scripts enforce code quality and test coverage standards.

### test

The `test` script executes the full test suite, covering unit and integration tests located in the `tests/` directory.

```bash
npm run test

```

### lint

The `lint` script runs linting rules to enforce code style consistency across the `src/` directory.

```bash
npm run lint

```

## Summary

- The root [`package.json`](https://github.com/every-app/open-seo/blob/main/package.json) defines **seven primary scripts**: `dev`, `build`, `start`, `type-check`, `test`, `lint`, and `prepare`
- **Development commands**: Use `npm run dev` for local development and `npm run start` for production execution
- **Build pipeline**: `npm run build` creates production assets, while `npm run type-check` validates TypeScript without emitting files
- **Quality gates**: `npm run test` and `npm run lint` ensure code reliability and style consistency
- The `prepare` script automates pre-publish tasks according to the every-app/open-seo source code configuration

## Frequently Asked Questions

### What is the difference between the `dev` and `start` scripts in open-seo?

The `dev` script launches a development server with hot-reloading and debugging features enabled, while `start` runs the pre-built application from the output directory intended for production environments.

### How does the `type-check` script work without generating files?

The `type-check` script executes the TypeScript compiler with the `--noEmit` flag as configured in [`tsconfig.json`](https://github.com/every-app/open-seo/blob/main/tsconfig.json), performing static type analysis without writing JavaScript files to disk.

### When does the `prepare` script run automatically?

The `prepare` script executes after `npm install` completes when the package is installed as a dependency, and also runs before `npm publish`, ensuring the package is built and validated before distribution.

### Where are the test files located that the `test` script executes?

According to the every-app/open-seo repository structure, the `test` script executes files located in the `tests/` directory at the repository root, covering both unit and integration test suites.