@teambit/harmony.content.cli-reference 1.95.32 → 1.95.33

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (9) hide show
  1. package/cli-reference.json +168 -52
  2. package/cli-reference.mdx +46 -75
  3. package/dist/cli-reference.json +168 -52
  4. package/dist/cli-reference.mdx.js +35 -136
  5. package/dist/cli-reference.mdx.js.map +1 -1
  6. package/package-tar/teambit-harmony.content.cli-reference-1.95.33.tgz +0 -0
  7. package/package.json +2 -2
  8. package/{preview-1655522887639.js → preview-1655782086029.js} +2 -2
  9. package/package-tar/teambit-harmony.content.cli-reference-1.95.32.tgz +0 -0
package/cli-reference.mdx CHANGED
@@ -12,15 +12,15 @@ all flags support glob patterns and {PARENT} {FILE_NAME} annotations
12
12
 
13
13
  `bit add [path...]`
14
14
 
15
- | **Option** | **Option alias** | **Description** |
16
- | ---------------------------------- | :--------------: | ---------------------------------------------------------------------------------------- |
17
- | `--id <name>` | `-i` | manually set component id |
18
- | `--main <file>` | `-m` | define entry point for the components |
19
- | `--tests <file>/"<file>,<file>"` | `-t` | specify test files to track. use quotation marks to list files or use a glob pattern |
20
- | `--namespace <namespace>` | `-n` | organize component in a namespace |
21
- | `--exclude <file>/"<file>,<file>"` | `-e` | exclude file from being tracked. use quotation marks to list files or use a glob pattern |
22
- | `--override <boolean>` | `-o` | override existing component if exists (default = false) |
23
- | `--scope <string>` | `-s` | sets the component's scope-name. if not entered, the default-scope will be used |
15
+ | **Option** | **Option alias** | **Description** |
16
+ | ---------------------------------- | :--------------: | ----------------------------------------------------------------------------------------------------- |
17
+ | `--id <name>` | `-i` | manually set component id |
18
+ | `--main <file>` | `-m` | define entry point for the components |
19
+ | `--tests <file>/"<file>,<file>"` | `-t` | LEGACY ONLY. specify test files to track. use quotation marks to list files or use a glob pattern |
20
+ | `--namespace <namespace>` | `-n` | organize component in a namespace |
21
+ | `--exclude <file>/"<file>,<file>"` | `-e` | LEGACY ONLY. exclude file from being tracked. use quotation marks to list files or use a glob pattern |
22
+ | `--override <boolean>` | `-o` | override existing component if exists (default = false) |
23
+ | `--scope <string>` | `-s` | sets the component's scope-name. if not entered, the default-scope will be used |
24
24
 
25
25
  ---
26
26
 
@@ -73,11 +73,7 @@ and a package.tgz file generated by pkg aspect.
73
73
 
74
74
  **Usage**: `aspect list [pattern]`
75
75
 
76
- **Description**: list all aspects configured on component(s)
77
- you can use a `<pattern>` for multiple component ids, such as `bit aspect list "org.scope/utils/**"`.
78
- use comma to separate patterns and "!" to exclude. e.g. "ui/\*\*, !ui/button"
79
- always wrap the pattern with quotes to avoid collision with shell commands.
80
- use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.
76
+ **Description**: list all aspects configured on component(s)
81
77
 
82
78
  | **Option** | **Option alias** | **Description** |
83
79
  | ---------- | :--------------: | ------------------------------------------------- |
@@ -85,9 +81,9 @@ use `bit pattern --help` to understand patterns better and `bit pattern <pattern
85
81
 
86
82
  ### aspect get
87
83
 
88
- **Usage**: `aspect get <component-id>`
84
+ **Usage**: `aspect get <component-name>`
89
85
 
90
- **Description**: show aspects' data and configuration of the given component
86
+ **Description**: list the aspects set on a component, as well as their config and data
91
87
 
92
88
  | **Option** | **Option alias** | **Description** |
93
89
  | ---------- | :--------------: | ------------------------------------------------- |
@@ -98,38 +94,19 @@ use `bit pattern --help` to understand patterns better and `bit pattern <pattern
98
94
 
99
95
  **Usage**: `aspect set <pattern> <aspect-id> [config]`
100
96
 
101
- **Description**: set an aspect to component(s) with optional config.
102
- enter the config as stringified JSON (e.g. '{"foo":"bar"}' ).
103
- if no config entered, the aspect will be set with empty config ({}).
104
- you can use a `<pattern>` for multiple component ids, such as `bit aspect set "org.scope/utils/**"`.
105
- use comma to separate patterns and "!" to exclude. e.g. "ui/\*\*, !ui/button"
106
- always wrap the pattern with quotes to avoid collision with shell commands.
107
- use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.
97
+ **Description**: set components with an aspect to extend their development tools, metadata and (possibly) artifacts
108
98
 
109
99
  ### aspect unset
110
100
 
111
101
  **Usage**: `aspect unset <pattern> <aspect-id>`
112
102
 
113
- **Description**: unset an aspect from component(s).
114
- you can use a `<pattern>` for multiple component ids, such as `bit aspect unset "org.scope/utils/**"`.
115
- use comma to separate patterns and "!" to exclude. e.g. "ui/\*\*, !ui/button"
116
- always wrap the pattern with quotes to avoid collision with shell commands.
117
- use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.
103
+ **Description**: unset an aspect from component(s).
118
104
 
119
105
  ### aspect update
120
106
 
121
107
  **Usage**: `aspect update <aspect-id> [pattern]`
122
108
 
123
- **Description**: update a version of an aspect
124
- default to all components using the aspect, unless "pattern" is provided.
125
- you can use a `<pattern>` for multiple component ids, such as `bit aspect update <aspect-id> "org.scope/utils/**"`.
126
- use comma to separate patterns and "!" to exclude. e.g. "ui/\*\*, !ui/button"
127
- always wrap the pattern with quotes to avoid collision with shell commands.
128
- use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.
129
-
130
- examples:
131
- "bit aspect update scope.org/aspect '**/ui/**'" - update "ui" components that use scope.org/aspect to the latest version
132
- "bit aspect update scope.org/aspect@2.0.0" - updates all components using scope.org/aspect to version 2.0.0.
109
+ **Description**: update a version of an aspect
133
110
 
134
111
  ---
135
112
 
@@ -157,7 +134,7 @@ examples:
157
134
 
158
135
  **Workspace only**: yes
159
136
  **Description**: manage capsules
160
- a capsule is a directory contains the component code, isolated from the workspace.
137
+ a capsule is a directory containing the component code, isolated from the workspace.
161
138
  normally, capsules are created during the build process, the component files are copied and the packages are installed
162
139
  via the configured package-manager. the purpose is to compile/test them in isolation to make sure they will work for
163
140
  other users after publishing/exporting them.
@@ -168,7 +145,7 @@ other users after publishing/exporting them.
168
145
 
169
146
  **Usage**: `capsule list`
170
147
 
171
- **Description**: list all capsules
148
+ **Description**: list the capsules generated for this workspace
172
149
 
173
150
  | **Option** | **Option alias** | **Description** |
174
151
  | ---------- | :--------------: | --------------- |
@@ -176,9 +153,9 @@ other users after publishing/exporting them.
176
153
 
177
154
  ### capsule create
178
155
 
179
- **Usage**: `capsule create [componentIds...]`
156
+ **Usage**: `capsule create [component-id...]`
180
157
 
181
- **Description**: create capsules
158
+ **Description**: create capsules for components
182
159
 
183
160
  | **Option** | **Option alias** | **Description** |
184
161
  | -------------------------- | :--------------: | ------------------------------------------------------------------------------------------------------- |
@@ -418,7 +395,7 @@ https://bit.dev/docs/config/bit-config
418
395
  ## diff
419
396
 
420
397
  **Workspace only**: yes
421
- **Description**: show diff between components files
398
+ **Description**: show the diff between the components' source files and config
422
399
  bit diff => compare all modified components to their model version
423
400
  bit diff [ids...] => compare the specified components against their modified states
424
401
  bit diff [id] [version] => compare the specified version to used or modified files
@@ -453,13 +430,9 @@ bit diff => compare all modified components to their model version
453
430
 
454
431
  **Alias**: `E`
455
432
  **Workspace only**: yes
456
- **Description**: replaces the components from the local scope with the corresponding packages
457
- you can use a `<pattern>` for multiple component ids, such as `bit eject "org.scope/utils/**"`.
458
- use comma to separate patterns and "!" to exclude. e.g. "ui/\*\*, !ui/button"
459
- always wrap the pattern with quotes to avoid collision with shell commands.
460
- use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.
433
+ **Description**: replace components maintained in the workspace with their corresponding packages
461
434
 
462
- `bit eject <pattern>`
435
+ `bit eject <component-pattern>`
463
436
 
464
437
  | **Option** | **Option alias** | **Description** |
465
438
  | -------------- | :--------------: | --------------------------------------------------------------------------------- |
@@ -556,7 +529,7 @@ you can use a pattern for multiple ids, such as bit export remote-scope "utils/\
556
529
  | `--rewire` | `-r` | LEGACY ONLY. when exporting to a different or new scope, replace import/require statements in the source code to match the new scope |
557
530
  | `--force` | `-f` | force changing a component remote without asking for a confirmation |
558
531
  | `--all-versions` | | export not only staged versions but all of them |
559
- | `--origin-directly` | | HARMONY ONLY. avoid export to the central hub, instead, export directly to the original scopes. not recommended! |
532
+ | `--origin-directly` | | EXPERIMENTAL. avoid export to the central hub, instead, export directly to the original scopes. not recommended! |
560
533
  | `--resume <string>` | | in case the previous export failed and suggested to resume with an export-id, enter the id |
561
534
  | `--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 |
562
535
  | `--json` | `-j` | show output in json format |
@@ -708,10 +681,10 @@ when no package is specified, all workspace dependencies are installed and all w
708
681
  ## link
709
682
 
710
683
  **Workspace only**: yes
711
- **Description**: link components and core aspects
684
+ **Description**: create links in the node_modules directory, to core aspects and to components in the workspace
712
685
  https://bit.dev/docs/workspace/component-links
713
686
 
714
- `bit link [ids...]`
687
+ `bit link [component-names...]`
715
688
 
716
689
  | **Option** | **Option alias** | **Description** |
717
690
  | ------------------------- | :--------------: | -------------------------------------------------------------------------------------------------------------- |
@@ -777,7 +750,7 @@ https://bit.dev/docs/reference/cli-reference#log
777
750
  ## login
778
751
 
779
752
  **Workspace only**: no
780
- **Description**: log the CLI into Bit Cloud
753
+ **Description**: log in to Bit cloud
781
754
 
782
755
  `bit login`
783
756
 
@@ -787,7 +760,7 @@ https://bit.dev/docs/reference/cli-reference#log
787
760
  | `--suppress-browser-launch` | | do not open a browser for authentication |
788
761
  | `--npmrc-path <path>` | | path to npmrc file to configure bit.cloud registry |
789
762
  | `--skip-registry-config` | | don't configure bit.cloud registry |
790
- | `--machine-name <string>` | | specify machine-name to pair with the token (useful for CI to avoid accidentally revoke the token) |
763
+ | `--machine-name <name>` | | specify machine-name to pair with the token (useful for CI to avoid accidentally revoke the token) |
791
764
 
792
765
  ---
793
766
 
@@ -832,11 +805,11 @@ merge changes of different component versions
832
805
  move files or directories of component(s)
833
806
  https://bit.dev/docs/workspace/moving-components
834
807
 
835
- `bit move <existing-dir> <new-dir>`
808
+ `bit move <current-component-dir> <new-component-dir>`
836
809
 
837
- | **Option** | **Option alias** | **Description** |
838
- | ------------- | :--------------: | ---------------------------------------------------------------------------------------------------------------------------- |
839
- | `--component` | `-c` | move component files that are spread over multiple directories to one directory. synopsis: `move <component-id> <directory>` |
810
+ | **Option** | **Option alias** | **Description** |
811
+ | ------------- | :--------------: | ----------------------------------------------------------------------------------------------------------------------------------------- |
812
+ | `--component` | `-c` | LEGACY ONLY. move component files that are spread over multiple directories to one directory. synopsis: `move <component-id> <directory>` |
840
813
 
841
814
  ---
842
815
 
@@ -951,16 +924,16 @@ for example: "http://localhost:3000", "file:///tmp/local-scope"
951
924
 
952
925
  **Alias**: `rm`
953
926
  **Workspace only**: no
954
- **Description**: remove component(s) from your workspace, or a remote scope
927
+ **Description**: remove component(s) from the workspace, or a remote scope
955
928
  https://bit.dev/docs/components/removing-components
956
929
  you can use a pattern for multiple ids, such as bit remove "utils/\*". (wrap the pattern with quotes to avoid collision with shell commands)
957
930
 
958
- `bit remove <ids...>`
931
+ `bit remove <component-ids...>`
959
932
 
960
933
  | **Option** | **Option alias** | **Description** |
961
934
  | ---------------- | :--------------: | ---------------------------------------------------------------------------------------------------------------------------------- |
962
935
  | `--remote` | `-r` | remove a component from a remote scope |
963
- | `--track` | `-t` | keep tracking component (default = false) |
936
+ | `--track` | `-t` | keep tracking component in .bitmap (default = false), helps transform a tagged-component to new |
964
937
  | `--delete-files` | `-d` | DEPRECATED (this is now the default). delete local component files |
965
938
  | `--keep-files` | | keep component files (just untrack the component) |
966
939
  | `--force` | `-f` | removes the component from the scope, even if used as a dependency. WARNING: components that depend on this component will corrupt |
@@ -971,17 +944,15 @@ you can use a pattern for multiple ids, such as bit remove "utils/\*". (wrap the
971
944
  ## rename
972
945
 
973
946
  **Workspace only**: no
974
- **Description**: EXPERIMENTAL. rename component. if tagged/exported, create a new component and deprecate the source-component
975
- the `<target-name>` should include the component-name only, without the scope-name.
976
- to assign a default-scope to this component, please use "--scope" flag
947
+ **Description**: EXPERIMENTAL. rename component. if tagged/exported, create a new component and deprecate the original component
977
948
 
978
- `bit rename <source-name> <target-name>`
949
+ `bit rename <current-name> <new-name>`
979
950
 
980
- | **Option** | **Option alias** | **Description** |
981
- | ------------------ | :--------------: | --------------------------------------------------------------------------------------- |
982
- | `--scope <string>` | `-s` | default scope for the newly created component |
983
- | `--path <string>` | `-p` | relative path in the workspace. by default the path is `<scope>/<namespace>/<name>` |
984
- | `--refactor` | `-r` | change the source code of all components using this component with the new package-name |
951
+ | **Option** | **Option alias** | **Description** |
952
+ | ------------------------ | :--------------: | ---------------------------------------------------------------------------------------- |
953
+ | `--scope <scope-name>` | `-s` | default scope for the newly created component |
954
+ | `--path <relative-path>` | `-p` | relative path in the workspace. by default the path is `<scope>/<namespace>/<name>` |
955
+ | `--refactor` | `-r` | update the import/require statements in all dependent components (in the same workspace) |
985
956
 
986
957
  ---
987
958
 
@@ -1147,7 +1118,7 @@ if no patterns are provided, it will tag all new and modified components.
1147
1118
  if patterns are entered, you can specify a version per pattern using "@" sign, e.g. bit tag foo@1.0.0 bar@minor baz@major
1148
1119
  https://bit.dev/components/tags
1149
1120
 
1150
- `bit tag [patterns...]`
1121
+ `bit tag [component-patterns...]`
1151
1122
 
1152
1123
  | **Option** | **Option alias** | **Description** |
1153
1124
  | ---------------------------- | :--------------: | ------------------------------------------------------------------------------------------------------------------------------ |
@@ -1248,11 +1219,11 @@ list components templates when inside bit-workspace (for bit-create), otherwise,
1248
1219
  ## untag
1249
1220
 
1250
1221
  **Workspace only**: yes
1251
- **Description**: revert versions tagged for component(s)
1222
+ **Description**: revert tagged or snapped versions for component(s)
1252
1223
  https://bit.dev/docs/components/tags#undoing-a-tag
1253
1224
  you can use a pattern for multiple ids, such as bit untag "utils/\*". (wrap the pattern with quotes to avoid collision with shell commands)
1254
1225
 
1255
- `bit untag [id] [version]`
1226
+ `bit untag [component-name] [component-version]`
1256
1227
 
1257
1228
  | **Option** | **Option alias** | **Description** |
1258
1229
  | ---------- | :--------------: | ----------------------------------------------------------------------------------------------------- |
@@ -1288,13 +1259,13 @@ you can use a pattern for multiple ids, such as bit untag "utils/\*". (wrap the
1288
1259
  ## watch
1289
1260
 
1290
1261
  **Workspace only**: yes
1291
- **Description**: watch a set of components
1262
+ **Description**: automatically recompile modified components (on save)
1292
1263
 
1293
1264
  `bit watch`
1294
1265
 
1295
1266
  | **Option** | **Option alias** | **Description** |
1296
1267
  | ------------------------ | :--------------: | ------------------------------------------------------------------------------------------------------------------------------------------------- |
1297
- | `--verbose` | `-v` | showing npm verbose output for inspection and prints stack trace |
1268
+ | `--verbose` | `-v` | show npm verbose output for inspection and print the stack trace |
1298
1269
  | `--skip-pre-compilation` | | skip the compilation step before starting to watch |
1299
1270
  | `--check-types [string]` | `-t` | EXPERIMENTAL. show errors/warnings for types. options are [file, project] to investigate only changed file or entire project. defaults to project |
1300
1271