> For the complete documentation index, see [llms.txt](https://docs.dappling.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dappling.network/builds/package-managers.md).

# Package managers

dAppling will automatically detect the package manager used in your project and install the dependencies during deployment. This detection is based on the lock file present in your project, which allows dAppling to infer the correct package manager to use.

## Supported package managers

Here are the supported package managers along with their install commands and versions

| Package Manger | Lock File           | Install Command | Versions |
| -------------- | ------------------- | --------------- | -------- |
| yarn           | `yarn.lock`         | `yarn install`  | 1        |
| npm            | `package-lock.json` | `npm install`   | 6,7,8    |
| pnpm           | `pnpm-lock.yaml`    | `pnpm install`  | 6,7,8    |
| bun            | `bun.lockb`         | `bun install`   | 1        |

\
While dAppling automatically selects the package manager based on your project's lock file, the specific version of that package manager is determined by the version information in the lock file or associated configuration files.

## Manually specifying a package manager

If you wish to manually specify a package manager for all deployments in your project, you can use the build setting in your project's [Build & Development Settings](/builds/configure-a-build.md). Follow these steps:

1. Navigate to your dashboard and select your project.
2. Select the Settings tab.
3. Add your desired install command. Once saved, it will be applied in your next deployment.

:cactus:*Fun Fact: The world's most poisonous plant is the castor bean plant; just one bean can kill a human.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dappling.network/builds/package-managers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.