@teambit/harmony.content.cli-reference 1.95.124 → 1.95.126

package/cli-reference.json

@@ -1873,126 +1873,6 @@
       }
     ]
   },
-  {
-    "name": "remove <component-pattern>",
-    "alias": "rm",
-    "options": [
-      [
-        "",
-        "soft",
-        "EXPERIMENTAL. mark the component as deleted. after tag/snap and export the remote will be updated"
-      ],
-      [
-        "r",
-        "remote",
-        "remove a component completely from a remote scope (Careful! this is a permanent change. prefer --soft and tag+export)"
-      ],
-      [
-        "",
-        "from-lane",
-        "revert to main if exists on currently checked out lane, otherwise, remove it"
-      ],
-      [
-        "t",
-        "track",
-        "keep tracking component in .bitmap (default = false), helps transform a tagged-component to new"
-      ],
-      [
-        "d",
-        "delete-files",
-        "DEPRECATED (this is now the default). delete local component files"
-      ],
-      [
-        "",
-        "keep-files",
-        "keep component files (just untrack the component)"
-      ],
-      [
-        "f",
-        "force",
-        "removes the component from the scope, even if used as a dependency. WARNING: components that depend on this component will corrupt"
-      ],
-      [
-        "s",
-        "silent",
-        "skip confirmation"
-      ]
-    ],
-    "description": "remove component(s) from the workspace, or a remote scope",
-    "extendedDescription": "",
-    "group": "collaborate",
-    "private": false,
-    "remoteOp": true,
-    "skipWorkspace": true,
-    "arguments": [
-      {
-        "name": "component-pattern",
-        "description": "component name, component id, or component pattern. use component pattern to select multiple components.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nwrap the pattern with quotes"
-      }
-    ]
-  },
-  {
-    "name": "resume-export <export-id> <remotes...>",
-    "alias": "",
-    "options": [],
-    "description": "EXPERIMENTAL. resume failed export",
-    "extendedDescription": "resume failed export to persist the pending objects on the given remotes.\nthe export-id is the id the client got in the error message during the failure.\nalternatively, exporting to any one of the failed scopes, throws server-is-busy error with the export-id",
-    "group": "collaborate",
-    "private": true,
-    "remoteOp": true
-  },
-  {
-    "name": "export [component-patterns...]",
-    "alias": "e",
-    "options": [
-      [
-        "e",
-        "eject",
-        "replace the exported components with their corresponding packages (to use these components without further maintaining them)"
-      ],
-      [
-        "a",
-        "all",
-        "export all components, including non-staged (useful when components in the remote scope are corrupted or missing)"
-      ],
-      [
-        "",
-        "all-versions",
-        "export not only staged versions but all of them (useful when versions in the remote scope are corrupted or missing)"
-      ],
-      [
-        "",
-        "origin-directly",
-        "EXPERIMENTAL. avoid export to the central hub, instead, export directly to the original scopes. not recommended!"
-      ],
-      [
-        "",
-        "resume <string>",
-        "in case the previous export failed and suggested to resume with an export-id, enter the id"
-      ],
-      [
-        "",
-        "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"
-      ],
-      [
-        "j",
-        "json",
-        "show output in json format"
-      ]
-    ],
-    "description": "export components from the workspace to remote scopes",
-    "extendedDescription": "bit export => export all staged components to their current scope, if checked out to a lane, export the lane as well\n  `bit export [id...]` => export the given ids to their current scope\n  you can use a pattern for multiple ids, such as bit export remote-scope \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
-    "group": "collaborate",
-    "private": false,
-    "remoteOp": true,
-    "arguments": [
-      {
-        "name": "component-patterns...",
-        "description": "component IDs, component names, or component patterns (separated by space). Use patterns to export groups of components using a common scope or namespace. E.g., \"utils/*\" (wrap with double quotes)"
-      }
-    ]
-  },
   {
     "name": "import [component-patterns...]",
     "alias": "",
@@ -2066,6 +1946,11 @@
         "",
         "fetch-deps",
         "fetch dependencies objects"
+      ],
+      [
+        "",
+        "track-only",
+        "do not write any file, just create .bitmap entries of the imported components"
       ]
     ],
     "description": "import components from their remote scopes to the local workspace",
@@ -2115,6 +2000,126 @@
     "group": "ungrouped",
     "private": true
   },
+  {
+    "name": "remove <component-pattern>",
+    "alias": "rm",
+    "options": [
+      [
+        "",
+        "soft",
+        "EXPERIMENTAL. mark the component as deleted. after tag/snap and export the remote will be updated"
+      ],
+      [
+        "r",
+        "remote",
+        "remove a component completely from a remote scope (Careful! this is a permanent change. prefer --soft and tag+export)"
+      ],
+      [
+        "",
+        "from-lane",
+        "revert to main if exists on currently checked out lane, otherwise, remove it"
+      ],
+      [
+        "t",
+        "track",
+        "keep tracking component in .bitmap (default = false), helps transform a tagged-component to new"
+      ],
+      [
+        "d",
+        "delete-files",
+        "DEPRECATED (this is now the default). delete local component files"
+      ],
+      [
+        "",
+        "keep-files",
+        "keep component files (just untrack the component)"
+      ],
+      [
+        "f",
+        "force",
+        "removes the component from the scope, even if used as a dependency. WARNING: components that depend on this component will corrupt"
+      ],
+      [
+        "s",
+        "silent",
+        "skip confirmation"
+      ]
+    ],
+    "description": "remove component(s) from the workspace, or a remote scope",
+    "extendedDescription": "",
+    "group": "collaborate",
+    "private": false,
+    "remoteOp": true,
+    "skipWorkspace": true,
+    "arguments": [
+      {
+        "name": "component-pattern",
+        "description": "component name, component id, or component pattern. use component pattern to select multiple components.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nwrap the pattern with quotes"
+      }
+    ]
+  },
+  {
+    "name": "resume-export <export-id> <remotes...>",
+    "alias": "",
+    "options": [],
+    "description": "EXPERIMENTAL. resume failed export",
+    "extendedDescription": "resume failed export to persist the pending objects on the given remotes.\nthe export-id is the id the client got in the error message during the failure.\nalternatively, exporting to any one of the failed scopes, throws server-is-busy error with the export-id",
+    "group": "collaborate",
+    "private": true,
+    "remoteOp": true
+  },
+  {
+    "name": "export [component-patterns...]",
+    "alias": "e",
+    "options": [
+      [
+        "e",
+        "eject",
+        "replace the exported components with their corresponding packages (to use these components without further maintaining them)"
+      ],
+      [
+        "a",
+        "all",
+        "export all components, including non-staged (useful when components in the remote scope are corrupted or missing)"
+      ],
+      [
+        "",
+        "all-versions",
+        "export not only staged versions but all of them (useful when versions in the remote scope are corrupted or missing)"
+      ],
+      [
+        "",
+        "origin-directly",
+        "EXPERIMENTAL. avoid export to the central hub, instead, export directly to the original scopes. not recommended!"
+      ],
+      [
+        "",
+        "resume <string>",
+        "in case the previous export failed and suggested to resume with an export-id, enter the id"
+      ],
+      [
+        "",
+        "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"
+      ],
+      [
+        "j",
+        "json",
+        "show output in json format"
+      ]
+    ],
+    "description": "export components from the workspace to remote scopes",
+    "extendedDescription": "bit export => export all staged components to their current scope, if checked out to a lane, export the lane as well\n  `bit export [id...]` => export the given ids to their current scope\n  you can use a pattern for multiple ids, such as bit export remote-scope \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
+    "group": "collaborate",
+    "private": false,
+    "remoteOp": true,
+    "arguments": [
+      {
+        "name": "component-patterns...",
+        "description": "component IDs, component names, or component patterns (separated by space). Use patterns to export groups of components using a common scope or namespace. E.g., \"utils/*\" (wrap with double quotes)"
+      }
+    ]
+  },
   {
     "name": "insights [names...]",
     "alias": "",

package/cli-reference.mdx

@@ -692,6 +692,7 @@ you can use a pattern for multiple ids, such as bit import "utils/\*". (wrap the
 | `--save-in-lane`                 |                  | EXPERIMENTAL. when checked out to a lane and the component is not on the remote-lane, save it in the lane (default to save on main)                                |
 | `--all-history`                  |                  | relevant for fetching all components objects. avoid optimizations, fetch all history versions, always                                                              |
 | `--fetch-deps`                   |                  | fetch dependencies objects                                                                                                                                         |
+| `--track-only`                   |                  | do not write any file, just create .bitmap entries of the imported components                                                                                      |
 
 ---
 

package/dist/cli-reference.json

@@ -1873,126 +1873,6 @@
             }
         ]
     },
-    {
-        "name": "remove <component-pattern>",
-        "alias": "rm",
-        "options": [
-            [
-                "",
-                "soft",
-                "EXPERIMENTAL. mark the component as deleted. after tag/snap and export the remote will be updated"
-            ],
-            [
-                "r",
-                "remote",
-                "remove a component completely from a remote scope (Careful! this is a permanent change. prefer --soft and tag+export)"
-            ],
-            [
-                "",
-                "from-lane",
-                "revert to main if exists on currently checked out lane, otherwise, remove it"
-            ],
-            [
-                "t",
-                "track",
-                "keep tracking component in .bitmap (default = false), helps transform a tagged-component to new"
-            ],
-            [
-                "d",
-                "delete-files",
-                "DEPRECATED (this is now the default). delete local component files"
-            ],
-            [
-                "",
-                "keep-files",
-                "keep component files (just untrack the component)"
-            ],
-            [
-                "f",
-                "force",
-                "removes the component from the scope, even if used as a dependency. WARNING: components that depend on this component will corrupt"
-            ],
-            [
-                "s",
-                "silent",
-                "skip confirmation"
-            ]
-        ],
-        "description": "remove component(s) from the workspace, or a remote scope",
-        "extendedDescription": "",
-        "group": "collaborate",
-        "private": false,
-        "remoteOp": true,
-        "skipWorkspace": true,
-        "arguments": [
-            {
-                "name": "component-pattern",
-                "description": "component name, component id, or component pattern. use component pattern to select multiple components.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nwrap the pattern with quotes"
-            }
-        ]
-    },
-    {
-        "name": "resume-export <export-id> <remotes...>",
-        "alias": "",
-        "options": [],
-        "description": "EXPERIMENTAL. resume failed export",
-        "extendedDescription": "resume failed export to persist the pending objects on the given remotes.\nthe export-id is the id the client got in the error message during the failure.\nalternatively, exporting to any one of the failed scopes, throws server-is-busy error with the export-id",
-        "group": "collaborate",
-        "private": true,
-        "remoteOp": true
-    },
-    {
-        "name": "export [component-patterns...]",
-        "alias": "e",
-        "options": [
-            [
-                "e",
-                "eject",
-                "replace the exported components with their corresponding packages (to use these components without further maintaining them)"
-            ],
-            [
-                "a",
-                "all",
-                "export all components, including non-staged (useful when components in the remote scope are corrupted or missing)"
-            ],
-            [
-                "",
-                "all-versions",
-                "export not only staged versions but all of them (useful when versions in the remote scope are corrupted or missing)"
-            ],
-            [
-                "",
-                "origin-directly",
-                "EXPERIMENTAL. avoid export to the central hub, instead, export directly to the original scopes. not recommended!"
-            ],
-            [
-                "",
-                "resume <string>",
-                "in case the previous export failed and suggested to resume with an export-id, enter the id"
-            ],
-            [
-                "",
-                "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"
-            ],
-            [
-                "j",
-                "json",
-                "show output in json format"
-            ]
-        ],
-        "description": "export components from the workspace to remote scopes",
-        "extendedDescription": "bit export => export all staged components to their current scope, if checked out to a lane, export the lane as well\n  `bit export [id...]` => export the given ids to their current scope\n  you can use a pattern for multiple ids, such as bit export remote-scope \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
-        "group": "collaborate",
-        "private": false,
-        "remoteOp": true,
-        "arguments": [
-            {
-                "name": "component-patterns...",
-                "description": "component IDs, component names, or component patterns (separated by space). Use patterns to export groups of components using a common scope or namespace. E.g., \"utils/*\" (wrap with double quotes)"
-            }
-        ]
-    },
     {
         "name": "import [component-patterns...]",
         "alias": "",
@@ -2066,6 +1946,11 @@
                 "",
                 "fetch-deps",
                 "fetch dependencies objects"
+            ],
+            [
+                "",
+                "track-only",
+                "do not write any file, just create .bitmap entries of the imported components"
             ]
         ],
         "description": "import components from their remote scopes to the local workspace",
@@ -2115,6 +2000,126 @@
         "group": "ungrouped",
         "private": true
     },
+    {
+        "name": "remove <component-pattern>",
+        "alias": "rm",
+        "options": [
+            [
+                "",
+                "soft",
+                "EXPERIMENTAL. mark the component as deleted. after tag/snap and export the remote will be updated"
+            ],
+            [
+                "r",
+                "remote",
+                "remove a component completely from a remote scope (Careful! this is a permanent change. prefer --soft and tag+export)"
+            ],
+            [
+                "",
+                "from-lane",
+                "revert to main if exists on currently checked out lane, otherwise, remove it"
+            ],
+            [
+                "t",
+                "track",
+                "keep tracking component in .bitmap (default = false), helps transform a tagged-component to new"
+            ],
+            [
+                "d",
+                "delete-files",
+                "DEPRECATED (this is now the default). delete local component files"
+            ],
+            [
+                "",
+                "keep-files",
+                "keep component files (just untrack the component)"
+            ],
+            [
+                "f",
+                "force",
+                "removes the component from the scope, even if used as a dependency. WARNING: components that depend on this component will corrupt"
+            ],
+            [
+                "s",
+                "silent",
+                "skip confirmation"
+            ]
+        ],
+        "description": "remove component(s) from the workspace, or a remote scope",
+        "extendedDescription": "",
+        "group": "collaborate",
+        "private": false,
+        "remoteOp": true,
+        "skipWorkspace": true,
+        "arguments": [
+            {
+                "name": "component-pattern",
+                "description": "component name, component id, or component pattern. use component pattern to select multiple components.\nuse comma to separate patterns and \"!\" to exclude. e.g. \"ui/**, !ui/button\"\nwrap the pattern with quotes"
+            }
+        ]
+    },
+    {
+        "name": "resume-export <export-id> <remotes...>",
+        "alias": "",
+        "options": [],
+        "description": "EXPERIMENTAL. resume failed export",
+        "extendedDescription": "resume failed export to persist the pending objects on the given remotes.\nthe export-id is the id the client got in the error message during the failure.\nalternatively, exporting to any one of the failed scopes, throws server-is-busy error with the export-id",
+        "group": "collaborate",
+        "private": true,
+        "remoteOp": true
+    },
+    {
+        "name": "export [component-patterns...]",
+        "alias": "e",
+        "options": [
+            [
+                "e",
+                "eject",
+                "replace the exported components with their corresponding packages (to use these components without further maintaining them)"
+            ],
+            [
+                "a",
+                "all",
+                "export all components, including non-staged (useful when components in the remote scope are corrupted or missing)"
+            ],
+            [
+                "",
+                "all-versions",
+                "export not only staged versions but all of them (useful when versions in the remote scope are corrupted or missing)"
+            ],
+            [
+                "",
+                "origin-directly",
+                "EXPERIMENTAL. avoid export to the central hub, instead, export directly to the original scopes. not recommended!"
+            ],
+            [
+                "",
+                "resume <string>",
+                "in case the previous export failed and suggested to resume with an export-id, enter the id"
+            ],
+            [
+                "",
+                "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"
+            ],
+            [
+                "j",
+                "json",
+                "show output in json format"
+            ]
+        ],
+        "description": "export components from the workspace to remote scopes",
+        "extendedDescription": "bit export => export all staged components to their current scope, if checked out to a lane, export the lane as well\n  `bit export [id...]` => export the given ids to their current scope\n  you can use a pattern for multiple ids, such as bit export remote-scope \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
+        "group": "collaborate",
+        "private": false,
+        "remoteOp": true,
+        "arguments": [
+            {
+                "name": "component-patterns...",
+                "description": "component IDs, component names, or component patterns (separated by space). Use patterns to export groups of components using a common scope or namespace. E.g., \"utils/*\" (wrap with double quotes)"
+            }
+        ]
+    },
     {
         "name": "insights [names...]",
         "alias": "",

package/dist/cli-reference.mdx.js

@@ -2918,7 +2918,20 @@ function MDXContent(_ref) {
   }), (0, _react2.mdx)("td", {
     parentName: "tr",
     "align": null
-  }, "fetch dependencies objects")))), (0, _react2.mdx)("hr", null), (0, _react2.mdx)("h2", null, "init"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("strong", {
+  }, "fetch dependencies objects")), (0, _react2.mdx)("tr", {
+    parentName: "tbody"
+  }, (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": null
+  }, (0, _react2.mdx)("inlineCode", {
+    parentName: "td"
+  }, "--track-only")), (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": "center"
+  }), (0, _react2.mdx)("td", {
+    parentName: "tr",
+    "align": null
+  }, "do not write any file, just create .bitmap entries of the imported components")))), (0, _react2.mdx)("hr", null), (0, _react2.mdx)("h2", null, "init"), (0, _react2.mdx)("p", null, (0, _react2.mdx)("strong", {
     parentName: "p"
   }, "Description"), ": create or reinitialize an empty workspace", (0, _react2.mdx)("br", {
     parentName: "p"