Esadax supports various package managers for dependency management, ensuring optimal build performance. This guide outlines the supported package managers, how they are detected, and how you can manually specify a package manager for your project or deployments.
The following table lists the package managers supported by Esadax, along with their install commands and versions:
| Package Manager | Lock File | Install Command | Supported Versions |
|---|---|---|---|
| Yarn | yarn.lock | yarn install |
1 |
| npm | package-lock.json | npm install |
8, 9, 10 |
| pnpm | pnpm-lock.yaml | pnpm install |
6, 7, 8, 9 |
| Bun | bun.lockb | bun install |
1 |
Esadax automatically detects the package manager based on the presence of a lock file in your project. If no lock file exists, it defaults to npm.
You can manually specify a package manager for your project or deployments. Here's how:
To specify a package manager for all deployments in your project:
pnpm install).To specify a package manager for a single deployment:
esadax.json file in your project root.installCommand property with the desired command (e.g., "pnpm install").The specific version of a package manager used depends on the lock file's lockfileVersion:
pnpm-lock.yaml with lockfileVersion: 9.0 uses pnpm 9.If no version is specified, Esadax defaults to using the latest compatible version based on Node.js versions.
Esadax simplifies dependency management by automatically detecting and using the appropriate package manager. For more details or assistance, feel free to ask!