# Use and adapt nsave

Use the documented interfaces and source layout for **nsave**. The sections below retain the README’s examples and configuration details.

## Commands

```
npm run dev        # http://localhost:3000 (or PORT=3001 npm run dev)
npm run build      # static prerender of all 26 routes
npm run typecheck
npm run inject-faq
```

## Commands in the root manifest

The captured [package.json](https://github.com/Up-to-code/nsave/blob/HEAD/package.json) declares the following scripts. Run them from the directory containing that manifest.

| Command | Script |
| --- | --- |
| `npm run dev` | `next dev` |
| `npm run build` | `next build` |
| `npm run start` | `next start` |
| `npm run typecheck` | `tsc --noEmit` |

## Troubleshoot a local change

1. Reproduce the smallest example from the [quick-start guide](/docs/up-to-code-nsave/quick-start-guide).
2. Compare required configuration and dependency versions with the README.
3. Check the linked issue tracker for the same error. Include the command, runtime version, and relevant error when reporting a problem; omit credentials.

## Source and help

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