buffrs remove - The Buffrs Book

Introduction
Summary
Getting Started
1. Installation
2. First Steps with Buffrs
Buffrs Guide
Buffrs Integrations
1. Cargo
2. Poetry
3. Npm
Buffrs Migration
1. Decomposition
2. Project Setup
3. Common Issues
4. Continuous Integration
Buffrs Reference
1. Editions
2. Specifying Dependencies
3. 1. Overriding Dependencies
4. The Manifest Format
5. The Lockfile Format
6. Configuration
7. Environment Variables
8. Build Configuration
9. Publishing on buff.rs
10. Package Name Specifications
11. Protocol Buffer Rules
12. Dependency Resolution
13. SemVer Compatibility
Buffrs Registry Reference
1. Authentication
2. Ownership
3. Storage Layers
4. Public Registry (buff.rs)
5. Categories
6. Self Hosting
7. 1. Registry Index
  2. Registry Web API
  3. Creating Teams
Buffrs Commands
1. General Commands
2. 1. buffrs
  2. buffrs help
  3. buffrs version
3. Build Commands
4. 1. buffrs clean
  2. buffrs doc
  3. buffrs generate
  4. buffrs list
5. Manifest Commands
6. 1. buffrs add
  2. buffrs lock
  3. buffrs remove
  4. buffrs tree
  5. buffrs update
7. Package Commands
9. Publishing Commands
10. 1. buffrs login
  2. buffrs logout
  3. buffrs publish
  4. buffrs yank
FAQ

buffrs remove

Removes an existing dependency from the package manifest.

Synopsis

buffrs remove <PACKAGE>

Description

The remove command is the recommended way to remove a dependency (identified by package name) from the manifest. It modifies the manifest and will produce an error if the specified package cannot be found. It implements the opposite operation from the add command.

Lockfile Interaction

Currently removing a dependency won't automatically update the lockfile (Proto.lock). This is planned to change, but for now make sure to follow up with buffrs install after adding a new dependency to make sure your lockfile is kept in sync.