@teambit/harmony.content.cli-reference 1.95.107 → 1.95.108

package/cli-reference.json

@@ -694,6 +694,21 @@
     "group": "general",
     "private": false
   },
+  {
+    "name": "globals",
+    "alias": "",
+    "options": [
+      [
+        "j",
+        "json",
+        "json format"
+      ]
+    ],
+    "description": "list all globals",
+    "extendedDescription": "",
+    "group": "workspace",
+    "private": false
+  },
   {
     "name": "show <component-name>",
     "alias": "",
@@ -751,7 +766,13 @@
       {
         "name": "get <component-name>",
         "alias": "",
-        "options": [],
+        "options": [
+          [
+            "",
+            "services <string>",
+            "show information about the specific services only. for multiple services, separate by a comma and wrap with quotes"
+          ]
+        ],
         "description": "show information about a component's env",
         "extendedDescription": "",
         "group": "development",
@@ -860,21 +881,6 @@
       }
     ]
   },
-  {
-    "name": "globals",
-    "alias": "",
-    "options": [
-      [
-        "j",
-        "json",
-        "json format"
-      ]
-    ],
-    "description": "list all globals",
-    "extendedDescription": "",
-    "group": "workspace",
-    "private": false
-  },
   {
     "name": "start [type] [pattern]",
     "alias": "c",
@@ -1216,131 +1222,192 @@
     ]
   },
   {
-    "name": "checkout <to> [component-pattern]",
-    "alias": "U",
+    "name": "create <template-name> <component-names...>",
+    "alias": "",
     "options": [
       [
-        "i",
-        "interactive-merge",
-        "when a component is modified and the merge process found conflicts, display options to resolve them"
+        "n",
+        "namespace <string>",
+        "sets the component's namespace and nested dirs inside the scope"
       ],
       [
-        "o",
-        "ours",
-        "in case of a conflict, override the used version with the current modification"
+        "s",
+        "scope <string>",
+        "sets the component's scope-name. if not entered, the default-scope will be used"
       ],
       [
-        "t",
-        "theirs",
-        "in case of a conflict, override the current modification with the specified version"
+        "a",
+        "aspect <string>",
+        "aspect-id of the template. helpful when multiple aspects use the same template name"
       ],
       [
-        "m",
-        "manual",
-        "in case of a conflict, leave the files with a conflict state to resolve them manually later"
+        "p",
+        "path <string>",
+        "relative path in the workspace. by default the path is `<scope>/<namespace>/<name>`"
       ],
       [
-        "r",
-        "reset",
-        "revert changes that were not snapped/tagged"
+        "e",
+        "env <string>",
+        "set the component's environment. (overrides the env from variants and the template)"
+      ]
+    ],
+    "description": "create a new component (source files and config) using a template.",
+    "extendedDescription": "",
+    "group": "development",
+    "private": false,
+    "arguments": [
+      {
+        "name": "template-name",
+        "description": "the template for generating the component \n(run 'bit templates' for a list of available templates)"
+      },
+      {
+        "name": "component-names...",
+        "description": "a list of component names to generate"
+      }
+    ],
+    "examples": [
+      {
+        "cmd": "bit create react ui/button",
+        "description": "creates a component named 'ui/button' using the 'react' template"
+      },
+      {
+        "cmd": "bit create react ui/button pages/register",
+        "description": "creates two components, 'ui/button' and 'pages/register', using the 'react' template"
+      },
+      {
+        "cmd": "bit create react ui/button --scope my-org.my-scope",
+        "description": "creates a component named 'ui/button' and sets it scope to 'my-org.my-scope'. \nby default, the scope is the `defaultScope` value, configured in your `workspace.jsonc`."
+      },
+      {
+        "cmd": "bit create react ui/button --env teambit.community/envs/community-react@1.95.13",
+        "description": "creates a component named 'ui/button' and sets it to use the 'community-react' env. \n(the template's default env is 'teambit.react/react')."
+      }
+    ]
+  },
+  {
+    "name": "templates",
+    "alias": "",
+    "options": [
+      [
+        "s",
+        "show-all",
+        "show hidden templates"
       ],
       [
         "a",
-        "all",
-        "all components"
-      ],
+        "aspect <aspect-id>",
+        "show templates provided by the aspect-id"
+      ]
+    ],
+    "description": "list templates for \"bit create\" and \"bit new\"",
+    "extendedDescription": "list components templates when inside bit-workspace (for bit-create), otherwise, list workspace templates (for bit-new)",
+    "group": "development",
+    "private": false
+  },
+  {
+    "name": "new <template-name> <workspace-name>",
+    "alias": "",
+    "options": [
       [
-        "e",
-        "entire-lane",
-        "write also new components that were introduced on the remote lane and do not exist locally"
+        "a",
+        "aspect <aspect-id>",
+        "aspect-id of the template. mandatory for non-core aspects. helpful for core aspects in case of a name collision"
       ],
       [
-        "v",
-        "verbose",
-        "showing verbose output for inspection"
+        "d",
+        "default-scope <scope-name>",
+        "set defaultScope in the new workspace.jsonc"
       ],
       [
         "",
-        "reset",
-        "DEPRECATED. run \"bit checkout reset\" instead"
+        "standalone",
+        "DEPRECATED. use --skip-git instead"
       ],
       [
-        "",
-        "skip-npm-install",
-        "DEPRECATED. use \"--skip-dependency-installation\" instead"
+        "s",
+        "skip-git",
+        "skip generation of Git repository"
+      ],
+      [
+        "e",
+        "empty",
+        "empty workspace with no components (relevant for templates that add components by default)"
       ],
       [
         "",
-        "skip-dependency-installation",
-        "do not install packages of the imported components"
+        "load-from <path-to-template>",
+        "path to the workspace containing the template. helpful during a development of a workspace-template"
       ]
     ],
-    "description": "switch between component versions or remove local changes",
-    "extendedDescription": "\n  `bit checkout <version> [component-pattern]` => checkout the specified ids (or all components when --all is used) to the specified version\n  `bit checkout head [component-pattern]` => checkout to the last snap/tag, omit [component-pattern] to checkout head for all\n  `bit checkout latest [component-pattern]` => checkout to the latest satisfying semver tag, omit [component-pattern] to checkout latest for all\n  `bit checkout reset [component-pattern]` => remove local modifications from the specified ids (or all components when --all is used)",
-    "group": "development",
+    "description": "create a new workspace from a template",
+    "extendedDescription": "",
+    "group": "start",
     "private": false,
     "arguments": [
       {
-        "name": "to",
-        "description": "permitted values: [head, latest, reset, specific-version]. 'head' - last snap/tag. 'latest' - semver latest tag. 'reset' - removes local changes"
+        "name": "template-name",
+        "description": "the name of the workspace template (run 'bit templates', outside of a workspace, to get a list of available templates)"
       },
       {
-        "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": "workspace-name",
+        "description": "the name for the new workspace and workspace directory"
       }
     ]
   },
   {
-    "name": "remove <component-pattern>",
-    "alias": "rm",
+    "name": "build [component-pattern]",
+    "alias": "",
     "options": [
       [
-        "",
-        "soft",
-        "EXPERIMENTAL. mark the component as deleted. after tag/snap and export the remote will be updated"
+        "a",
+        "all",
+        "DEPRECATED. use --unmodified"
       ],
       [
-        "r",
-        "remote",
-        "remove a component completely from a remote scope (Careful! this is a permanent change. prefer --soft and tag+export)"
+        "u",
+        "unmodified",
+        "include unmodified components (by default, only new and modified components are built)"
+      ],
+      [
+        "d",
+        "dev",
+        "run the pipeline in dev mode"
       ],
       [
         "",
-        "from-lane",
-        "revert to main if exists on currently checked out lane, otherwise, remove it"
+        "install",
+        "install core aspects in capsules"
       ],
       [
-        "t",
-        "track",
-        "keep tracking component in .bitmap (default = false), helps transform a tagged-component to new"
+        "",
+        "reuse-capsules",
+        "avoid deleting the capsules root-dir before starting the build"
       ],
       [
-        "d",
-        "delete-files",
-        "DEPRECATED (this is now the default). delete local component files"
+        "",
+        "tasks <string>",
+        "build the specified task(s) only. for multiple tasks, separate by a comma and wrap with quotes.\nspecify the task-name (e.g. \"TypescriptCompiler\") or the task-aspect-id (e.g. teambit.compilation/compiler)"
       ],
       [
         "",
-        "keep-files",
-        "keep component files (just untrack the component)"
+        "cache-packages-on-capsule-root",
+        "set the package-manager cache on the capsule root"
       ],
       [
-        "f",
-        "force",
-        "removes the component from the scope, even if used as a dependency. WARNING: components that depend on this component will corrupt"
+        "",
+        "list-tasks <string>",
+        "list tasks of an env or a component-id for each one of the pipelines: build, tag and snap"
       ],
       [
-        "s",
-        "silent",
-        "skip confirmation"
+        "",
+        "skip-tests",
+        "skip running component tests during tag process"
       ]
     ],
-    "description": "remove component(s) from the workspace, or a remote scope",
+    "description": "run set of tasks for build",
     "extendedDescription": "",
-    "group": "collaborate",
+    "group": "development",
     "private": false,
-    "remoteOp": true,
-    "skipWorkspace": true,
     "arguments": [
       {
         "name": "component-pattern",
@@ -1349,64 +1416,74 @@
     ]
   },
   {
-    "name": "resume-export <export-id> <remotes...>",
+    "name": "artifacts <component-pattern>",
     "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)"
+        "",
+        "aspect <aspect-id>",
+        "show/download only artifacts generated by this aspect-id"
       ],
       [
         "",
-        "all-versions",
-        "export not only staged versions but all of them (useful when versions in the remote scope are corrupted or missing)"
+        "task <task-id>",
+        "show/download only artifacts generated by this task-id"
       ],
       [
         "",
-        "origin-directly",
-        "EXPERIMENTAL. avoid export to the central hub, instead, export directly to the original scopes. not recommended!"
+        "files <glob>",
+        "show/download only artifacts matching the given files or the glob pattern (wrap glob patterns in quotes)"
       ],
       [
         "",
-        "resume <string>",
-        "in case the previous export failed and suggested to resume with an export-id, enter the id"
+        "out-dir <string>",
+        "download the files to the specified dir"
+      ]
+    ],
+    "description": "list and download components artifacts",
+    "extendedDescription": "artifacts are created on isolated capsules during tag or snap commands.\nexample of artifacts are dists files generated by a compiler, a JUnit.xml file generated by a tester\nand a package.tgz file generated by pkg aspect.\n",
+    "group": "development",
+    "private": false,
+    "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": "compile [component-names...]",
+    "alias": "",
+    "options": [
+      [
+        "c",
+        "changed",
+        "compile only new and modified components"
       ],
       [
-        "",
-        "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"
+        "v",
+        "verbose",
+        "show more data, such as, dist paths"
       ],
       [
         "j",
         "json",
-        "show output in json format"
+        "return the compile results in json format"
+      ],
+      [
+        "d",
+        "delete-dist-dir",
+        "delete existing dist folder before writing new compiled files"
       ]
     ],
-    "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",
+    "description": "compile components in the workspace",
+    "extendedDescription": "",
+    "group": "development",
     "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": "component-names...",
+        "description": "a list of component names or component IDs (defaults to all components)"
       }
     ]
   },
@@ -1426,309 +1503,252 @@
     "private": true
   },
   {
-    "name": "import [component-patterns...]",
-    "alias": "",
+    "name": "install [packages...]",
+    "alias": "in",
     "options": [
-      [
-        "p",
-        "path <path>",
-        "import components into a specific directory (a relative path in the workspace)"
-      ],
-      [
-        "o",
-        "objects",
-        "import components objects to the local scope without checkout (without writing them to the file system). This is a default behavior for import with no id argument"
-      ],
-      [
-        "d",
-        "display-dependencies",
-        "display the imported dependencies"
-      ],
-      [
-        "O",
-        "override",
-        "override local changes"
-      ],
       [
         "v",
-        "verbose",
-        "show verbose output for inspection"
-      ],
-      [
-        "j",
-        "json",
-        "return the output as JSON"
-      ],
-      [
-        "",
-        "skip-npm-install",
-        "DEPRECATED. use \"--skip-dependency-installation\" instead"
+        "variants <variants>",
+        "add packages to specific variants"
       ],
       [
-        "",
-        "skip-dependency-installation",
-        "do not install packages of the imported components"
+        "t",
+        "type [lifecycleType]",
+        "\"runtime\" (default) or \"peer\" (dev is not a valid option)"
       ],
       [
-        "m",
-        "merge [strategy]",
-        "merge local changes with the imported version. strategy should be \"theirs\", \"ours\" or \"manual\""
+        "u",
+        "update-existing [updateExisting]",
+        "update existing dependencies version and types"
       ],
       [
         "",
-        "dependencies",
-        "EXPERIMENTAL. import all dependencies and write them to the workspace"
+        "save-prefix [savePrefix]",
+        "set the prefix to use when adding dependency to workspace.jsonc"
       ],
       [
         "",
-        "dependents",
-        "EXPERIMENTAL. import components found while traversing from the given ids upwards to the workspace components"
+        "skip-dedupe [skipDedupe]",
+        "do not dedupe dependencies on installation"
       ],
       [
         "",
-        "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)"
+        "skip-import [skipImport]",
+        "do not import bit objects post installation"
       ],
       [
         "",
-        "all-history",
-        "relevant for fetching all components objects. avoid optimizations, fetch all history versions, always"
+        "skip-compile [skipCompile]",
+        "do not compile components"
       ],
       [
         "",
-        "fetch-deps",
-        "fetch dependencies objects"
+        "add-missing-peers [addMissingPeers]",
+        "install all missing peer dependencies"
       ]
     ],
-    "description": "import components from their remote scopes to the local workspace",
-    "extendedDescription": "https://bit.dev/docs/components/importing-components\nyou can use a pattern for multiple ids, such as bit import \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
-    "group": "collaborate",
+    "description": "installs workspace dependencies",
+    "extendedDescription": "when no package is specified, all workspace dependencies are installed and all workspace components are imported.",
+    "group": "development",
     "private": false,
-    "remoteOp": true,
     "arguments": [
       {
-        "name": "component-patterns...",
-        "description": "component IDs or component patterns (separated by space). Use patterns to import groups of components using a common scope or namespace. E.g., \"utils/*\" (wrap with double quotes)"
+        "name": "packages...",
+        "description": "a list of packages to install (separated by spaces)"
       }
     ]
   },
   {
-    "name": "fetch [ids...]",
-    "alias": "",
+    "name": "uninstall [packages...]",
+    "alias": "un",
+    "options": [],
+    "description": "uninstall dependencies",
+    "extendedDescription": "",
+    "group": "development",
+    "private": false
+  },
+  {
+    "name": "update",
+    "alias": "up",
     "options": [
       [
-        "l",
-        "lanes",
-        "EXPERIMENTAL. fetch component objects from lanes. note, it does not save the remote lanes objects locally, only the refs"
-      ],
-      [
-        "c",
-        "components",
-        "fetch components"
-      ],
-      [
-        "j",
-        "json",
-        "return the output as JSON"
-      ],
-      [
-        "",
-        "from-original-scopes",
-        "fetch indirect dependencies from their original scope as opposed to from their dependents"
+        "y",
+        "yes",
+        "automatically update all outdated packages"
       ]
     ],
-    "description": "fetch remote objects and store locally",
-    "extendedDescription": "for lanes, use \"/\" as a separator between the remote and the lane name, e.g. teambit.ui/fix-button",
-    "group": "ungrouped",
-    "private": true
+    "description": "update dependencies",
+    "extendedDescription": "",
+    "group": "development",
+    "private": false
   },
   {
-    "name": "create <template-name> <component-names...>",
+    "name": "link [component-names...]",
     "alias": "",
     "options": [
       [
-        "n",
-        "namespace <string>",
-        "sets the component's namespace and nested dirs inside the scope"
+        "j",
+        "json",
+        "return the output as JSON"
       ],
       [
-        "s",
-        "scope <string>",
-        "sets the component's scope-name. if not entered, the default-scope will be used"
+        "",
+        "verbose",
+        "verbose output"
       ],
       [
-        "a",
-        "aspect <string>",
-        "aspect-id of the template. helpful when multiple aspects use the same template name"
+        "r",
+        "rewire",
+        "Replace relative paths with module paths in code (e.g. \"../foo\" => \"@bit/foo\")"
       ],
       [
-        "p",
-        "path <string>",
-        "relative path in the workspace. by default the path is `<scope>/<namespace>/<name>`"
+        "",
+        "target <dir>",
+        "EXPERIMENTAL. link to an external directory (similar to npm-link) so other projects could use these components"
       ],
       [
-        "e",
-        "env <string>",
-        "set the component's environment. (overrides the env from variants and the template)"
+        "",
+        "skip-fetching-objects",
+        "skip fetch missing objects from remotes before linking"
       ]
     ],
-    "description": "create a new component (source files and config) using a template.",
-    "extendedDescription": "",
+    "description": "create links in the node_modules directory, to core aspects and to components in the workspace",
+    "extendedDescription": "https://bit.dev/docs/workspace/component-links",
     "group": "development",
     "private": false,
     "arguments": [
-      {
-        "name": "template-name",
-        "description": "the template for generating the component \n(run 'bit templates' for a list of available templates)"
-      },
       {
         "name": "component-names...",
-        "description": "a list of component names to generate"
-      }
-    ],
-    "examples": [
-      {
-        "cmd": "bit create react ui/button",
-        "description": "creates a component named 'ui/button' using the 'react' template"
-      },
-      {
-        "cmd": "bit create react ui/button pages/register",
-        "description": "creates two components, 'ui/button' and 'pages/register', using the 'react' template"
-      },
-      {
-        "cmd": "bit create react ui/button --scope my-org.my-scope",
-        "description": "creates a component named 'ui/button' and sets it scope to 'my-org.my-scope'. \nby default, the scope is the `defaultScope` value, configured in your `workspace.jsonc`."
-      },
-      {
-        "cmd": "bit create react ui/button --env teambit.community/envs/community-react@1.95.13",
-        "description": "creates a component named 'ui/button' and sets it to use the 'community-react' env. \n(the template's default env is 'teambit.react/react')."
+        "description": "names or IDs of the components to link"
       }
     ]
   },
   {
-    "name": "templates",
-    "alias": "",
+    "name": "checkout <to> [component-pattern]",
+    "alias": "U",
     "options": [
       [
-        "s",
-        "show-all",
-        "show hidden templates"
+        "i",
+        "interactive-merge",
+        "when a component is modified and the merge process found conflicts, display options to resolve them"
       ],
       [
-        "a",
-        "aspect <aspect-id>",
-        "show templates provided by the aspect-id"
-      ]
-    ],
-    "description": "list templates for \"bit create\" and \"bit new\"",
-    "extendedDescription": "list components templates when inside bit-workspace (for bit-create), otherwise, list workspace templates (for bit-new)",
-    "group": "development",
-    "private": false
-  },
-  {
-    "name": "new <template-name> <workspace-name>",
-    "alias": "",
-    "options": [
+        "o",
+        "ours",
+        "in case of a conflict, override the used version with the current modification"
+      ],
       [
-        "a",
-        "aspect <aspect-id>",
-        "aspect-id of the template. mandatory for non-core aspects. helpful for core aspects in case of a name collision"
+        "t",
+        "theirs",
+        "in case of a conflict, override the current modification with the specified version"
       ],
       [
-        "d",
-        "default-scope <scope-name>",
-        "set defaultScope in the new workspace.jsonc"
+        "m",
+        "manual",
+        "in case of a conflict, leave the files with a conflict state to resolve them manually later"
       ],
       [
-        "",
-        "standalone",
-        "DEPRECATED. use --skip-git instead"
+        "r",
+        "reset",
+        "revert changes that were not snapped/tagged"
       ],
       [
-        "s",
-        "skip-git",
-        "skip generation of Git repository"
+        "a",
+        "all",
+        "all components"
       ],
       [
         "e",
-        "empty",
-        "empty workspace with no components (relevant for templates that add components by default)"
+        "entire-lane",
+        "write also new components that were introduced on the remote lane and do not exist locally"
+      ],
+      [
+        "v",
+        "verbose",
+        "showing verbose output for inspection"
       ],
       [
         "",
-        "load-from <path-to-template>",
-        "path to the workspace containing the template. helpful during a development of a workspace-template"
+        "reset",
+        "DEPRECATED. run \"bit checkout reset\" instead"
+      ],
+      [
+        "",
+        "skip-npm-install",
+        "DEPRECATED. use \"--skip-dependency-installation\" instead"
+      ],
+      [
+        "",
+        "skip-dependency-installation",
+        "do not install packages of the imported components"
       ]
     ],
-    "description": "create a new workspace from a template",
-    "extendedDescription": "",
-    "group": "start",
+    "description": "switch between component versions or remove local changes",
+    "extendedDescription": "\n  `bit checkout <version> [component-pattern]` => checkout the specified ids (or all components when --all is used) to the specified version\n  `bit checkout head [component-pattern]` => checkout to the last snap/tag, omit [component-pattern] to checkout head for all\n  `bit checkout latest [component-pattern]` => checkout to the latest satisfying semver tag, omit [component-pattern] to checkout latest for all\n  `bit checkout reset [component-pattern]` => remove local modifications from the specified ids (or all components when --all is used)",
+    "group": "development",
     "private": false,
     "arguments": [
       {
-        "name": "template-name",
-        "description": "the name of the workspace template (run 'bit templates', outside of a workspace, to get a list of available templates)"
+        "name": "to",
+        "description": "permitted values: [head, latest, reset, specific-version]. 'head' - last snap/tag. 'latest' - semver latest tag. 'reset' - removes local changes"
       },
       {
-        "name": "workspace-name",
-        "description": "the name for the new workspace and workspace directory"
+        "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": "build [component-pattern]",
-    "alias": "",
+    "name": "remove <component-pattern>",
+    "alias": "rm",
     "options": [
       [
-        "a",
-        "all",
-        "DEPRECATED. use --unmodified"
-      ],
-      [
-        "u",
-        "unmodified",
-        "include unmodified components (by default, only new and modified components are built)"
+        "",
+        "soft",
+        "EXPERIMENTAL. mark the component as deleted. after tag/snap and export the remote will be updated"
       ],
       [
-        "d",
-        "dev",
-        "run the pipeline in dev mode"
+        "r",
+        "remote",
+        "remove a component completely from a remote scope (Careful! this is a permanent change. prefer --soft and tag+export)"
       ],
       [
         "",
-        "install",
-        "install core aspects in capsules"
+        "from-lane",
+        "revert to main if exists on currently checked out lane, otherwise, remove it"
       ],
       [
-        "",
-        "reuse-capsules",
-        "avoid deleting the capsules root-dir before starting the build"
+        "t",
+        "track",
+        "keep tracking component in .bitmap (default = false), helps transform a tagged-component to new"
       ],
       [
-        "",
-        "tasks <string>",
-        "build the specified task(s) only. for multiple tasks, separate by a comma and wrap with quotes.\nspecify the task-name (e.g. \"TypescriptCompiler\") or the task-aspect-id (e.g. teambit.compilation/compiler)"
+        "d",
+        "delete-files",
+        "DEPRECATED (this is now the default). delete local component files"
       ],
       [
         "",
-        "cache-packages-on-capsule-root",
-        "set the package-manager cache on the capsule root"
+        "keep-files",
+        "keep component files (just untrack the component)"
       ],
       [
-        "",
-        "list-tasks <string>",
-        "list tasks of an env or a component-id for each one of the pipelines: build, tag and snap"
+        "f",
+        "force",
+        "removes the component from the scope, even if used as a dependency. WARNING: components that depend on this component will corrupt"
       ],
       [
-        "",
-        "skip-tests",
-        "skip running component tests during tag process"
+        "s",
+        "silent",
+        "skip confirmation"
       ]
     ],
-    "description": "run set of tasks for build",
+    "description": "remove component(s) from the workspace, or a remote scope",
     "extendedDescription": "",
-    "group": "development",
+    "group": "collaborate",
     "private": false,
+    "remoteOp": true,
+    "skipWorkspace": true,
     "arguments": [
       {
         "name": "component-pattern",
@@ -1737,197 +1757,183 @@
     ]
   },
   {
-    "name": "artifacts <component-pattern>",
+    "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)"
+      ],
       [
         "",
-        "aspect <aspect-id>",
-        "show/download only artifacts generated by this aspect-id"
+        "all-versions",
+        "export not only staged versions but all of them (useful when versions in the remote scope are corrupted or missing)"
       ],
       [
         "",
-        "task <task-id>",
-        "show/download only artifacts generated by this task-id"
+        "origin-directly",
+        "EXPERIMENTAL. avoid export to the central hub, instead, export directly to the original scopes. not recommended!"
       ],
       [
         "",
-        "files <glob>",
-        "show/download only artifacts matching the given files or the glob pattern (wrap glob patterns in quotes)"
+        "resume <string>",
+        "in case the previous export failed and suggested to resume with an export-id, enter the id"
       ],
       [
         "",
-        "out-dir <string>",
-        "download the files to the specified dir"
+        "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": "list and download components artifacts",
-    "extendedDescription": "artifacts are created on isolated capsules during tag or snap commands.\nexample of artifacts are dists files generated by a compiler, a JUnit.xml file generated by a tester\nand a package.tgz file generated by pkg aspect.\n",
-    "group": "development",
+    "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-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": "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": "compile [component-names...]",
+    "name": "import [component-patterns...]",
     "alias": "",
     "options": [
       [
-        "c",
-        "changed",
-        "compile only new and modified components"
+        "p",
+        "path <path>",
+        "import components into a specific directory (a relative path in the workspace)"
+      ],
+      [
+        "o",
+        "objects",
+        "import components objects to the local scope without checkout (without writing them to the file system). This is a default behavior for import with no id argument"
+      ],
+      [
+        "d",
+        "display-dependencies",
+        "display the imported dependencies"
+      ],
+      [
+        "O",
+        "override",
+        "override local changes"
       ],
       [
         "v",
         "verbose",
-        "show more data, such as, dist paths"
+        "show verbose output for inspection"
       ],
       [
         "j",
         "json",
-        "return the compile results in json format"
+        "return the output as JSON"
       ],
       [
-        "d",
-        "delete-dist-dir",
-        "delete existing dist folder before writing new compiled files"
-      ]
-    ],
-    "description": "compile components in the workspace",
-    "extendedDescription": "",
-    "group": "development",
-    "private": false,
-    "arguments": [
-      {
-        "name": "component-names...",
-        "description": "a list of component names or component IDs (defaults to all components)"
-      }
-    ]
-  },
-  {
-    "name": "install [packages...]",
-    "alias": "in",
-    "options": [
-      [
-        "v",
-        "variants <variants>",
-        "add packages to specific variants"
+        "",
+        "skip-npm-install",
+        "DEPRECATED. use \"--skip-dependency-installation\" instead"
       ],
       [
-        "t",
-        "type [lifecycleType]",
-        "\"runtime\" (default) or \"peer\" (dev is not a valid option)"
+        "",
+        "skip-dependency-installation",
+        "do not install packages of the imported components"
       ],
       [
-        "u",
-        "update-existing [updateExisting]",
-        "update existing dependencies version and types"
+        "m",
+        "merge [strategy]",
+        "merge local changes with the imported version. strategy should be \"theirs\", \"ours\" or \"manual\""
       ],
       [
         "",
-        "save-prefix [savePrefix]",
-        "set the prefix to use when adding dependency to workspace.jsonc"
+        "dependencies",
+        "EXPERIMENTAL. import all dependencies and write them to the workspace"
       ],
       [
         "",
-        "skip-dedupe [skipDedupe]",
-        "do not dedupe dependencies on installation"
+        "dependents",
+        "EXPERIMENTAL. import components found while traversing from the given ids upwards to the workspace components"
       ],
       [
         "",
-        "skip-import [skipImport]",
-        "do not import bit objects post installation"
+        "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)"
       ],
       [
         "",
-        "skip-compile [skipCompile]",
-        "do not compile components"
+        "all-history",
+        "relevant for fetching all components objects. avoid optimizations, fetch all history versions, always"
       ],
       [
         "",
-        "add-missing-peers [addMissingPeers]",
-        "install all missing peer dependencies"
+        "fetch-deps",
+        "fetch dependencies objects"
       ]
     ],
-    "description": "installs workspace dependencies",
-    "extendedDescription": "when no package is specified, all workspace dependencies are installed and all workspace components are imported.",
-    "group": "development",
+    "description": "import components from their remote scopes to the local workspace",
+    "extendedDescription": "https://bit.dev/docs/components/importing-components\nyou can use a pattern for multiple ids, such as bit import \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
+    "group": "collaborate",
     "private": false,
+    "remoteOp": true,
     "arguments": [
       {
-        "name": "packages...",
-        "description": "a list of packages to install (separated by spaces)"
+        "name": "component-patterns...",
+        "description": "component IDs or component patterns (separated by space). Use patterns to import groups of components using a common scope or namespace. E.g., \"utils/*\" (wrap with double quotes)"
       }
     ]
   },
   {
-    "name": "uninstall [packages...]",
-    "alias": "un",
-    "options": [],
-    "description": "uninstall dependencies",
-    "extendedDescription": "",
-    "group": "development",
-    "private": false
-  },
-  {
-    "name": "update",
-    "alias": "up",
-    "options": [
-      [
-        "y",
-        "yes",
-        "automatically update all outdated packages"
-      ]
-    ],
-    "description": "update dependencies",
-    "extendedDescription": "",
-    "group": "development",
-    "private": false
-  },
-  {
-    "name": "link [component-names...]",
+    "name": "fetch [ids...]",
     "alias": "",
     "options": [
       [
-        "j",
-        "json",
-        "return the output as JSON"
-      ],
-      [
-        "",
-        "verbose",
-        "verbose output"
+        "l",
+        "lanes",
+        "EXPERIMENTAL. fetch component objects from lanes. note, it does not save the remote lanes objects locally, only the refs"
       ],
       [
-        "r",
-        "rewire",
-        "Replace relative paths with module paths in code (e.g. \"../foo\" => \"@bit/foo\")"
+        "c",
+        "components",
+        "fetch components"
       ],
       [
-        "",
-        "target <dir>",
-        "EXPERIMENTAL. link to an external directory (similar to npm-link) so other projects could use these components"
+        "j",
+        "json",
+        "return the output as JSON"
       ],
       [
         "",
-        "skip-fetching-objects",
-        "skip fetch missing objects from remotes before linking"
+        "from-original-scopes",
+        "fetch indirect dependencies from their original scope as opposed to from their dependents"
       ]
     ],
-    "description": "create links in the node_modules directory, to core aspects and to components in the workspace",
-    "extendedDescription": "https://bit.dev/docs/workspace/component-links",
-    "group": "development",
-    "private": false,
-    "arguments": [
-      {
-        "name": "component-names...",
-        "description": "names or IDs of the components to link"
-      }
-    ]
+    "description": "fetch remote objects and store locally",
+    "extendedDescription": "for lanes, use \"/\" as a separator between the remote and the lane name, e.g. teambit.ui/fix-button",
+    "group": "ungrouped",
+    "private": true
   },
   {
     "name": "insights [names...]",
@@ -2355,7 +2361,7 @@
     "private": true
   },
   {
-    "name": "merge [values...]",
+    "name": "merge [ids...]",
     "alias": "",
     "options": [
       [
@@ -2409,8 +2415,8 @@
         "EXPERIMENTAL. override the default message for the auto snap"
       ]
     ],
-    "description": "merge changes of different component versions",
-    "extendedDescription": "merge changes of different component versions\n  `bit merge <version> [ids...]` => merge changes of the given version into the checked out version\n  `bit merge [ids...]` => EXPERIMENTAL. merge changes of the remote head into local, optionally use '--abort' or '--resolve'\n  you can use a pattern for multiple ids, such as bit merge 0.0.1 \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
+    "description": "merge changes of the remote head into local",
+    "extendedDescription": "merge changes of the remote head into local, optionally use '--abort' or '--resolve\nyou can use a pattern for multiple ids, such as bit merge \"utils/*\". (wrap the pattern with quotes to avoid collision with shell commands)",
     "group": "development",
     "private": false
   },