Mark components as deleted on the remote
$bit delete <component-pattern>
Additional Notes
to remove components from your local workspace only, use "bit remove" command.
this command marks the components as deleted, and after snap/tag and export they will be marked as deleted from the remote scope as well.
Arguments
| Argument | Description | Required |
|---|---|---|
| component-pattern | component name, component id, or component pattern. use component pattern to select multiple components. wrap the pattern with quotes. use comma to separate patterns and "!" to exclude. e.g. "ui/**, !ui/button". use '$' prefix to filter by states/attributes, e.g. '$deprecated', '$modified' or '$env:teambit.react/react'. use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern. | ✅ |
Options
| Option | Option Alias | Description | Value Type |
|---|---|---|---|
| --lane | - | when on a lane, delete the component from this lane only. avoid merging it to main or other lanes | boolean |
| --update-main | - | EXPERIMENTAL. delete component/s on the main lane after merging this lane into main | boolean |
| --range | - | EXPERIMENTAL. enter a Semver range to delete specific tags (cannot be used for snaps). see https://www.npmjs.com/package/semver#ranges for the range syntax | string |
| --silent | -s | skip confirmation | boolean |
| --hard | - | NOT-RECOMMENDED. delete a component completely from a remote scope. careful! this is a permanent change that could corrupt dependents. | boolean |
| --force | -f | relevant for --hard. allow the deletion even if used as a dependency. WARNING: components that depend on this component will corrupt | boolean |
