> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/sfp/development/dependency-management/shrink-dependencies.md).

# Shrink Dependencies

The `sfp dependency:shrink` command optimizes your project's dependency declarations by removing redundant transitive dependencies from your `sfdx-project.json`. This results in a cleaner project configuration with only the necessary direct dependencies declared for each package.

#### Usage

```bash
# Create a shrunk version of the project configuration
sfp dependency:shrink

# Overwrite the existing sfdx-project.json with shrunk dependencies
sfp dependency:shrink --overwrite
```

#### Flags

| Flag                           | Description                                                                  | Required |
| ------------------------------ | ---------------------------------------------------------------------------- | -------- |
| `-o`, `--overwrite`            | Overwrites the existing sfdx-project.json file with the shrunk configuration | No       |
| `-v`, `--targetdevhubusername` | Username or alias of the target Dev Hub org                                  | Yes      |
| `--loglevel`                   | Logging level (trace, debug, info, warn, error, fatal)                       | No       |

#### Behavior

* Without `--overwrite`, creates a new file at `./project-config/sfdx-project.min.json`
* With `--overwrite`, backs up existing `sfdx-project.json` to `./project-config/sfdx-project.json.bak` and overwrites the original
* Removes transitive dependencies that are already covered by direct dependencies
* Preserves external dependency mappings

### External Dependencies Configuration

External dependencies can be configured in your `sfdx-project.json` file using the `plugins.sfp` section. This is particularly useful for managed packages or packages from other Dev Hubs that your project depends on.

#### Configuration Format

```json
{
  "packageDirectories": [...],
  "plugins": {
    "sfp": {
      "externalDependencyMap": {
        "package-name": [
          {
            "package": "04tXXXXXXXXXXXXXXX",
            "versionNumber": "1.0.0.LATEST"
          }
        ]
      }
    }
  }
}
```

#### Example

```json
{
  "plugins": {
    "sfp": {
      "externalDependencyMap": {
        "trigger-framework": [
          {
            "package": "0H1000XRTCam",
            "versionNumber": "1.0.3.LATEST"
          }
        ]
      }
    }
  }
}
```

#### Notes

* External dependencies must be defined with their 04t IDs (subscriber package version IDs)
* The `versionNumber` can use `.LATEST` to automatically use the latest version that matches the major.minor.patch pattern
* External dependencies are preserved during both shrink and expand operations
* These dependencies are automatically included when calculating transitive dependencies


---

# 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.flxbl.io/flxbl/sfp/development/dependency-management/shrink-dependencies.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.