Create a new component (source files and config) using a template.
$bit create <template-name> <component-names...>
Arguments
| Argument | Description | Required |
|---|---|---|
| template-name | the template for generating the component (run 'bit templates' for a list of available templates) | ✅ |
| component-names... | a list of component names to generate | ✅ |
Options
| Option | Option Alias | Description | Value Type |
|---|---|---|---|
| --namespace | -n | sets the component's namespace and nested dirs inside the scope | string |
| --scope | -s | sets the component's scope-name. if not entered, the default-scope will be used | string |
| --aspect | -a | aspect-id of the template. helpful when multiple aspects use the same template name | string |
| --template | -t | env-id of the template. alias for --aspect. | string |
| --path | -p | relative path in the workspace. by default the path is `<scope>/<namespace>/<name>` | string |
| --env | -e | set the component's environment. (overrides the env from variants and the template) | string |
| --force | -f | replace existing files at the target location | boolean |
