@teambit/harmony.content.cli-reference 1.95.232 → 1.95.234

package/cli-reference.docs.mdx

@@ -1,5 +1,5 @@
 ---
-description: 'Bit command synopses. Bit version: 0.2.53'
+description: 'Bit command synopses. Bit version: 0.2.55'
 labels: ['cli', 'mdx', 'docs']
 ---
       

package/cli-reference.json

@@ -1608,7 +1608,7 @@
       ]
     ],
     "description": "automatically recompile modified components (on save)",
-    "extendedDescription": "by default, the watcher use polling, although it causes a high CPU usage.\nit's needed due to a bug (fixed in master but not released yet) in Chokidar package, which is used by Bit watcher.\nfor small projects though it should be ok to use the fsevents.\nto use fsevents, run \"bit config set watch_use_fsevents true\".",
+    "extendedDescription": "by default, the watcher doesn't use polling, to keep the CPU idle.\nif this doesn't work well for you, run \"bit config set watch_use_polling true\" to use polling.",
     "group": "development",
     "private": false
   },
@@ -2734,7 +2734,7 @@
       ]
     ],
     "description": "tag components from a bare-scope by using build artifacts from previous snap and running the deploy-pipeline only",
-    "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the tag.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string;    // ids always have scope, so it's safe to parse them from string\n  dependencies?: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester@1.0.0]\n  versionToTag?: string;  // specific version (e.g. '1.0.0') or semver (e.g. 'minor', 'patch')\n  prereleaseId?: string;  // applicable when versionToTag is a pre-release. (e.g. \"dev\", for 1.0.0-dev.1)\n  message?: string;       // tag-message.\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"dependencies\":[\"ci.remote/comp1@0.0.2\"]}]'\n",
+    "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the tag.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string;    // ids always have scope, so it's safe to parse them from string\n  dependencies?: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester^@1.0.0, teambit/linter~@0.0.1]\n  versionToTag?: string;  // specific version (e.g. '1.0.0') or semver (e.g. 'minor', 'patch')\n  prereleaseId?: string;  // applicable when versionToTag is a pre-release. (e.g. \"dev\", for 1.0.0-dev.1)\n  message?: string;       // tag-message.\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"dependencies\":[\"ci.remote/comp1@0.0.2\"]}]'\n",
     "group": "development",
     "private": true,
     "remoteOp": true

package/cli-reference.mdx

@@ -1956,10 +1956,8 @@ list components templates when inside bit-workspace (for bit-create), otherwise,
 ## watch
 
 **Description**: automatically recompile modified components (on save)  
-by default, the watcher use polling, although it causes a high CPU usage.  
-it's needed due to a bug (fixed in master but not released yet) in Chokidar package, which is used by Bit watcher.  
-for small projects though it should be ok to use the fsevents.  
-to use fsevents, run "bit config set watch_use_fsevents true".
+by default, the watcher doesn't use polling, to keep the CPU idle.  
+if this doesn't work well for you, run "bit config set watch_use_polling true" to use polling.
 
 `bit watch`
 

package/dist/cli-reference.docs.mdx

@@ -1,5 +1,5 @@
 ---
-description: 'Bit command synopses. Bit version: 0.2.53'
+description: 'Bit command synopses. Bit version: 0.2.55'
 labels: ['cli', 'mdx', 'docs']
 ---
       

package/dist/cli-reference.json

@@ -1608,7 +1608,7 @@
             ]
         ],
         "description": "automatically recompile modified components (on save)",
-        "extendedDescription": "by default, the watcher use polling, although it causes a high CPU usage.\nit's needed due to a bug (fixed in master but not released yet) in Chokidar package, which is used by Bit watcher.\nfor small projects though it should be ok to use the fsevents.\nto use fsevents, run \"bit config set watch_use_fsevents true\".",
+        "extendedDescription": "by default, the watcher doesn't use polling, to keep the CPU idle.\nif this doesn't work well for you, run \"bit config set watch_use_polling true\" to use polling.",
         "group": "development",
         "private": false
     },
@@ -2734,7 +2734,7 @@
             ]
         ],
         "description": "tag components from a bare-scope by using build artifacts from previous snap and running the deploy-pipeline only",
-        "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the tag.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string;    // ids always have scope, so it's safe to parse them from string\n  dependencies?: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester@1.0.0]\n  versionToTag?: string;  // specific version (e.g. '1.0.0') or semver (e.g. 'minor', 'patch')\n  prereleaseId?: string;  // applicable when versionToTag is a pre-release. (e.g. \"dev\", for 1.0.0-dev.1)\n  message?: string;       // tag-message.\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"dependencies\":[\"ci.remote/comp1@0.0.2\"]}]'\n",
+        "extendedDescription": "this command should be running from a new bare scope, it first imports the components it needs and then processes the tag.\nthe input data is a stringified JSON of an array of the following object.\n{\n  componentId: string;    // ids always have scope, so it's safe to parse them from string\n  dependencies?: string[]; // e.g. [teambit/compiler@1.0.0, teambit/tester^@1.0.0, teambit/linter~@0.0.1]\n  versionToTag?: string;  // specific version (e.g. '1.0.0') or semver (e.g. 'minor', 'patch')\n  prereleaseId?: string;  // applicable when versionToTag is a pre-release. (e.g. \"dev\", for 1.0.0-dev.1)\n  message?: string;       // tag-message.\n}\nan example of the final data: '[{\"componentId\":\"ci.remote2/comp-b\",\"dependencies\":[\"ci.remote/comp1@0.0.2\"]}]'\n",
         "group": "development",
         "private": true,
         "remoteOp": true

package/dist/cli-reference.mdx.js

@@ -9864,13 +9864,9 @@ function MDXContent(_ref) {
     parentName: "p"
   }, "Description"), ": automatically recompile modified components (on save)", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "by default, the watcher use polling, although it causes a high CPU usage.", (0, _react2.mdx)("br", {
+  }), "\n", "by default, the watcher doesn't use polling, to keep the CPU idle.", (0, _react2.mdx)("br", {
     parentName: "p"
-  }), "\n", "it's needed due to a bug (fixed in master but not released yet) in Chokidar package, which is used by Bit watcher.", (0, _react2.mdx)("br", {
-    parentName: "p"
-  }), "\n", "for small projects though it should be ok to use the fsevents.", (0, _react2.mdx)("br", {
-    parentName: "p"
-  }), "\n", "to use fsevents, run \"bit config set watch_use_fsevents true\"."), (0, _react2.mdx)("p", null, (0, _react2.mdx)("inlineCode", {
+  }), "\n", "if this doesn't work well for you, run \"bit config set watch_use_polling true\" to use polling."), (0, _react2.mdx)("p", null, (0, _react2.mdx)("inlineCode", {
     parentName: "p"
   }, "bit watch")), (0, _react2.mdx)("table", null, (0, _react2.mdx)("thead", {
     parentName: "table"