Eject components configuration (create a `component.json` file)
$bit eject-conf <pattern>
Additional Notes
note this can be reversed at any time by snapping/tagging changes and deleting the component.json file
you can use a `<pattern>` for multiple component ids, such as `bit eject-conf "org.scope/utils/**"`.
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'.
always wrap the pattern with single quotes to avoid collision with shell commands.
use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.
Options
| Option | Option Alias | Description | Value Type |
|---|---|---|---|
| --propagate | -p | mark propagate true in the config file, so that component.json configs will be merge with workspace configs | boolean |
| --override | -o | override file if exist | boolean |
