# This is a library

> When a project looks like a library rather than an app, the cabinet says so at import. What it looks at and what to do.

Source: https://livops.dev/en/docs/error-library

A library is code other projects install: an npm package, a Ruby gem, a PyPI package, a Maven artifact. Deploy one and the build passes, but nothing is left running — the program ends at once. That is why the cabinet says so before the build. It is not a refusal: you can still deploy.

## What it looks at

| Kind | Sign |
| --- | --- |
| npm | `package.json` has `peerDependencies` and `exports`/`types`, no `start` script, no server or bot library |
| Ruby gem | a `*.gemspec` at the root, no `config.ru` and no Rails |
| PyPI | `pyproject.toml` has `[build-system]`, no command (`[project.scripts]`), no `main.py`/`app.py`/`bot.py` |
| Maven | `pom.xml` has neither `spring-boot-maven-plugin` nor `Main-Class` |

A project that also works as a site (a Jekyll theme with its docs, say) is not marked.

## What to do

- If it holds an example or an app (`example/`, `playground/`), set that folder as the **Root folder**.
- Or write the start command in **Settings → Start**.
- If the app that uses the library lives in another repository, deploy that one.
