Export components from the workspace to remote scopes
$bit export [component-patterns...]
$bit e [component-patterns...]
Additional Notes
bit export => export all staged snaps/tags of components to their remote scope. if checked out to a lane, export the lane as well
`bit export [pattern...]` => export components included by the pattern to their remote scope (we recommend not using a pattern in
most scenarios so that all changes are exported simultaneously)
you can use a pattern for multiple ids, such as bit export "utils/*". (wrap the pattern with quotes to avoid collision with shell commands)
Arguments
| Argument | Description | Required |
|---|---|---|
| component-patterns... | (not recommended) 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 `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern. |
Options
| Option | Option Alias | Description | Value Type |
|---|---|---|---|
| --eject | -e | after export, remove the components from the workspace and install them as packages | boolean |
| --all | -a | export all components, including non-staged (useful when components in the remote scope are corrupted or missing) | boolean |
| --all-versions | - | export not only staged versions but all of them (useful when versions in the remote scope are corrupted or missing) | boolean |
| --origin-directly | - | EXPERIMENTAL. avoid export to the central hub, instead, export directly to the original scopes. not recommended! | boolean |
| --resume | - | in case the previous export failed and suggested to resume with an export-id, enter the id | string |
| --head-only | - | EXPERIMENTAL. in case previous export failed and locally it shows exported and only one snap/tag was created, try using this flag | boolean |
| --ignore-missing-artifacts | - | EXPERIMENTAL. don't throw an error when artifact files are missing. not recommended, unless you're sure the artifacts are in the remote | boolean |
| --fork-lane-new-scope | - | allow exporting a forked lane into a different scope than the original scope | boolean |
| --open-browser | - | open a browser once the export is completed in the cloud job url | boolean |
| --json | -j | show output in json format | boolean |
