# Run a first expense-tracker example

Start with the smallest workflow described by the README for **expense-tracker**. Complete [installation and configuration](/docs/up-to-code-expense-tracker/installation-guide) first.

## Start the project

Complete [installation](/docs/up-to-code-expense-tracker/installation-guide), then run the root manifest script:

```sh
npm run start
```

Follow the local URL, emulator, or process status printed by the development tool. The manifest establishes the command; it does not establish application credentials or a deployed service.

## Verify your changes

The root manifest provides this check:

```sh
npm run test
```

Read any errors before continuing. Build and type checks verify source consistency; exercise the README example to verify the behavior you need.

## Next task

[Read the usage guide](/docs/up-to-code-expense-tracker/usage-guide) for the documented components, configuration, and source layout.

## Source and help

- [GitHub repository](https://github.com/Up-to-code/expense-tracker)
- [Original README](https://github.com/Up-to-code/expense-tracker/blob/master/README.md)
- [Issues and existing reports](https://github.com/Up-to-code/expense-tracker/issues)
- [Open the project website](https://expense-tracker-five-inky.vercel.app)