@teambit/isolator 1.0.310 → 1.0.311

package/artifacts/__bit_junit.xml

@@ -1,4 +1,4 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <testsuites tests="0" failures="0" errors="0" skipped="0">
-  <testsuite name="teambit.component/isolator@1.0.310" tests="0" failures="0" errors="0" skipped="0"/>
+  <testsuite name="teambit.component/isolator@1.0.311" tests="0" failures="0" errors="0" skipped="0"/>
 </testsuites>

package/artifacts/preview/teambit_component_isolator-preview.js

@@ -1 +1 @@
-!function(e,t){"object"==typeof exports&&"object"==typeof module?module.exports=t():"function"==typeof define&&define.amd?define([],t):"object"==typeof exports?exports["teambit.component/isolator-preview"]=t():e["teambit.component/isolator-preview"]=t()}(self,(()=>(()=>{"use strict";var e={63609:(e,t,o)=>{var n={id:"teambit.component/isolator@1.0.310",homepage:"https://bit.cloud/teambit/component/isolator",exported:!0};function r(){const e=a(o(41594));return r=function(){return e},e}function a(e){return e&&e.__esModule?e:{default:e}}Object.defineProperty(t,"__esModule",{value:!0}),t.Logo=void 0,r.__bit_component=n,a.__bit_component=n;const s=()=>r().default.createElement("div",{style:{height:"100%",display:"flex",justifyContent:"center"}},r().default.createElement("img",{style:{width:70},src:"https://static.bit.dev/extensions-icons/isolator.svg"}));s.__bit_component=n,t.Logo=s},41594:e=>{e.exports=React}},t={};function o(n){var r=t[n];if(void 0!==r)return r.exports;var a=t[n]={exports:{}};return e[n](a,a.exports,o),a.exports}o.d=(e,t)=>{for(var n in t)o.o(t,n)&&!o.o(e,n)&&Object.defineProperty(e,n,{enumerable:!0,get:t[n]})},o.o=(e,t)=>Object.prototype.hasOwnProperty.call(e,t),o.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})};var n={};o.r(n),o.d(n,{compositions:()=>m,compositions_metadata:()=>h,overview:()=>f});var r={};o.r(r),o.d(r,{default:()=>u});var a=o(63609);o(41594);const s=MdxJsReact,i=TeambitMdxUiMdxScopeContext;var l=["components"];function p(){return p=Object.assign?Object.assign.bind():function(e){for(var t=1;t<arguments.length;t++){var o=arguments[t];for(var n in o)({}).hasOwnProperty.call(o,n)&&(e[n]=o[n])}return e},p.apply(null,arguments)}var c={},d="wrapper";function u(e){var t=e.components,o=function(e,t){if(null==e)return{};var o,n,r=function(e,t){if(null==e)return{};var o={};for(var n in e)if({}.hasOwnProperty.call(e,n)){if(t.indexOf(n)>=0)continue;o[n]=e[n]}return o}(e,t);if(Object.getOwnPropertySymbols){var a=Object.getOwnPropertySymbols(e);for(n=0;n<a.length;n++)o=a[n],t.indexOf(o)>=0||{}.propertyIsEnumerable.call(e,o)&&(r[o]=e[o])}return r}(e,l);return(0,s.mdx)(d,p({},c,o,{components:t,mdxType:"MDXLayout"}),(0,s.mdx)(i.MDXScopeProvider,{components:{},mdxType:"MDXScopeProvider"},(0,s.mdx)("h2",null,"Isolate a component"),(0,s.mdx)("pre",null,(0,s.mdx)("code",{parentName:"pre",className:"language-bash"},"bit create-capsule ui/button\n")),(0,s.mdx)("h2",null,"Entities"),(0,s.mdx)("h3",null,"Capsule"),(0,s.mdx)("p",null,"Bit implements a filesystem capsule, which is an isolated folder containing the component files.\nCapsules include the component files and links to other capsules that include the component's dependencies."),(0,s.mdx)("h3",null,"Network"),(0,s.mdx)("p",null,"A network is a group of capsules, related to one another by their dependencies.\nA network includes a graph of all seed components given to it, as well as a list of the capsules."),(0,s.mdx)("p",null,"Example:"),(0,s.mdx)("pre",null,(0,s.mdx)("code",{parentName:"pre",className:"language-javascript"},"const Network = {\n  graph: Graph,\n  capsules: CapsuleList,\n};\n")),(0,s.mdx)("h2",null,"API"),(0,s.mdx)("p",null,"The exact particularities of this API are beyond the scope of this readme. Instead, this document opts to\nprovide a general description of the methods of this API and their purpose."),(0,s.mdx)("h3",null,"Isolator.isolateComponents"),(0,s.mdx)("p",null,"This method receives a list of components, create capsule for the components and write the components data into the capsule.\nIt returns a list of capsules.")))}u.isMDXComponent=!0;const m=[a],f=[r],h={compositions:[{displayName:"Logo",identifier:"Logo"}]};return n})()));
+!function(e,t){"object"==typeof exports&&"object"==typeof module?module.exports=t():"function"==typeof define&&define.amd?define([],t):"object"==typeof exports?exports["teambit.component/isolator-preview"]=t():e["teambit.component/isolator-preview"]=t()}(self,(()=>(()=>{"use strict";var e={84794:(e,t,o)=>{var n={id:"teambit.component/isolator@1.0.311",homepage:"https://bit.cloud/teambit/component/isolator",exported:!0};function r(){const e=a(o(41594));return r=function(){return e},e}function a(e){return e&&e.__esModule?e:{default:e}}Object.defineProperty(t,"__esModule",{value:!0}),t.Logo=void 0,r.__bit_component=n,a.__bit_component=n;const s=()=>r().default.createElement("div",{style:{height:"100%",display:"flex",justifyContent:"center"}},r().default.createElement("img",{style:{width:70},src:"https://static.bit.dev/extensions-icons/isolator.svg"}));s.__bit_component=n,t.Logo=s},41594:e=>{e.exports=React}},t={};function o(n){var r=t[n];if(void 0!==r)return r.exports;var a=t[n]={exports:{}};return e[n](a,a.exports,o),a.exports}o.d=(e,t)=>{for(var n in t)o.o(t,n)&&!o.o(e,n)&&Object.defineProperty(e,n,{enumerable:!0,get:t[n]})},o.o=(e,t)=>Object.prototype.hasOwnProperty.call(e,t),o.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})};var n={};o.r(n),o.d(n,{compositions:()=>m,compositions_metadata:()=>h,overview:()=>f});var r={};o.r(r),o.d(r,{default:()=>u});var a=o(84794);o(41594);const s=MdxJsReact,i=TeambitMdxUiMdxScopeContext;var l=["components"];function p(){return p=Object.assign?Object.assign.bind():function(e){for(var t=1;t<arguments.length;t++){var o=arguments[t];for(var n in o)({}).hasOwnProperty.call(o,n)&&(e[n]=o[n])}return e},p.apply(null,arguments)}var c={},d="wrapper";function u(e){var t=e.components,o=function(e,t){if(null==e)return{};var o,n,r=function(e,t){if(null==e)return{};var o={};for(var n in e)if({}.hasOwnProperty.call(e,n)){if(t.indexOf(n)>=0)continue;o[n]=e[n]}return o}(e,t);if(Object.getOwnPropertySymbols){var a=Object.getOwnPropertySymbols(e);for(n=0;n<a.length;n++)o=a[n],t.indexOf(o)>=0||{}.propertyIsEnumerable.call(e,o)&&(r[o]=e[o])}return r}(e,l);return(0,s.mdx)(d,p({},c,o,{components:t,mdxType:"MDXLayout"}),(0,s.mdx)(i.MDXScopeProvider,{components:{},mdxType:"MDXScopeProvider"},(0,s.mdx)("h2",null,"Isolate a component"),(0,s.mdx)("pre",null,(0,s.mdx)("code",{parentName:"pre",className:"language-bash"},"bit create-capsule ui/button\n")),(0,s.mdx)("h2",null,"Entities"),(0,s.mdx)("h3",null,"Capsule"),(0,s.mdx)("p",null,"Bit implements a filesystem capsule, which is an isolated folder containing the component files.\nCapsules include the component files and links to other capsules that include the component's dependencies."),(0,s.mdx)("h3",null,"Network"),(0,s.mdx)("p",null,"A network is a group of capsules, related to one another by their dependencies.\nA network includes a graph of all seed components given to it, as well as a list of the capsules."),(0,s.mdx)("p",null,"Example:"),(0,s.mdx)("pre",null,(0,s.mdx)("code",{parentName:"pre",className:"language-javascript"},"const Network = {\n  graph: Graph,\n  capsules: CapsuleList,\n};\n")),(0,s.mdx)("h2",null,"API"),(0,s.mdx)("p",null,"The exact particularities of this API are beyond the scope of this readme. Instead, this document opts to\nprovide a general description of the methods of this API and their purpose."),(0,s.mdx)("h3",null,"Isolator.isolateComponents"),(0,s.mdx)("p",null,"This method receives a list of components, create capsule for the components and write the components data into the capsule.\nIt returns a list of capsules.")))}u.isMDXComponent=!0;const m=[a],f=[r],h={compositions:[{displayName:"Logo",identifier:"Logo"}]};return n})()));

package/artifacts/schema.json

@@ -66,7 +66,8 @@
               "character": 1
             },
             "raw": "/**\n * collection of isolated components (capsules).\n * normally, \"seeders\" are the components that this network was created for.\n * \"graphCapsules\" is the graph created from the seeders and it includes also the dependencies.\n *\n * however, during \"bit build\"/\"bit tag\"/\"bit snap\", things are more complex because there is one more variable in the\n * picture, which is the \"env\". the Network is created per env.\n * in practice, for \"build-task\", a task is called per env, and the network passed to the task is relevant to that env.\n * the \"originalSeeders\" are the ones the network was created for, but only for this env.\n * the \"seeders\" are similar to the \"graphCapsules\" above, which contains also the dependencies, but only for this env.\n * the \"graphCapsules\" is the entire graph, including capsules from other envs.\n *\n * for example:\n * comp1 depends on comp2. comp1 env is \"react\". comp2 env is \"aspect\".\n *\n * when the user is running \"bit build comp1\", two `Network` instances will be created with the following:\n * Network for \"react\" env:  originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\n * Network for \"aspect\" env: originalSeeders: [], seeders: ['comp2'], graphCapsules: ['comp2'].\n *\n * on the other hand, when the user is running \"bit capsule create comp1\", only one `Network` instance is created:\n * Network: originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\n *\n * (as a side note, another implementation was attempt to have the \"seeders\" as the original-seeders for build,\n * however, it's failed. see https://github.com/teambit/bit/pull/5407 for more details).\n *\n *\n * A more detailed explanation about the \"seeders\" vs \"originalSeeders\" vs \"graphCapsules\" is provided below:\n * an example: comp1 -> comp2 -> comp3 (as in comp1 uses comp2, comp2 uses comp3).\n * I changed only comp2.\n * From comp2 perspective, comp1 is a “dependent”, comp3 is a “dependency”.\n *\n * When I run bit build with no args, it finds only one modified component: comp2, however, it doesn’t stop here. It also look for the dependents, in this case, comp1. So the seeders of this bit-build command are two: “comp1” and “comp2\".\n * The reason why the dependents are included is because you modified comp2, it’s possible you broke comp1. We want to build comp1 as well to make sure it’s still okay.\n * (btw, bit test command also include dependents when it provided with no args).\n *\n * Keep in mind that also bit tag normally runs on the dependents as well (when it runs the build pipeline), because these are the “auto-tag”.\n * With these two seeders it builds the graph. The graph calculates all the dependencies of the given seeders recursively. Eventually, it puts them in an instance of Network class.\n * In our case, if all components use the same env, the Network consist of:\n * seedersCapsules:          [comp1, comp2]\n * originalSeedersCapsules:  [comp1, comp2]\n * graphCapsules:            [comp1, comp2, comp3].\n *\n * It gets more complex when multiple envs involved.\n * Imagine that comp1 uses env1, comp2 uses env2 and comp3 uses env3.\n * Because bit build runs the tasks per env, it needs to create 3 networks. Each per env.\n * The “seeders” refer to the seeders of the same env and includes only components from the same env.\n * The “originalSeeders” refer to the ones that originally started the build command and are from the same env.\n * Network1:\n * seedersCapsules:          [comp1]\n * originalSeedersCapsules:  [comp1]\n * graphCapsules:            [comp1, comp2, comp3].\n * Network2:\n * seedersCapsules:          [comp2]\n * originalSeedersCapsules:  [comp2]\n * graphCapsules:            [comp2, comp3].\n * Network3:\n * seedersCapsules:          [comp3]\n * originalSeedersCapsules:  []\n * graphCapsules:            [comp3].\n * As you can see, in network3, the originalSeeders is empty, because comp3 wasn’t part of the original seeders.\n * These 3 networks are created for build-pipeline. This pipeline asks for all components in the graph and then create the network per env.\n * Snap/Tag pipelines are different. They ask only for the components about to tag/snap, which are the original-seeders, and create the network per env. For them, we end up with 2 network instances only. network1 and network2. Also, the seedersCapsules and originalSeedersCapsules are the same because we create the network instances out of the seeders only, without the dependencies.\n * A build-task provides context with a network instance to the execute() method. (it also provide Component[] which are the “seeders”. not “originalSeeders”).\n *\n * Each build-task can decide on what components to operate. It has 3 options:\n * run on graphCapsules. If you do that, you risk running your task multiple times on the same components. In the example above, a task of build-pipeline, will run 3 times on comp3, because this component is part of the graphCapsules in each one of the network instance. So this is probably not recommended for most tasks.\n * run on seedersCapsules. With this option you make sure that your task is running for each one of the capsules and it runs only once. This is good for example for the compiler task. It needs to make sure all capsules are built. Otherwise, if it’s running only on originalSeedersCapsules, the comp3 won’t be compiled, the dists will be missing and comp2 won’t be able to run its tests.\n * run on originalSeedersCapsules . With this option you ensure that your task runs only on the ids you started with and you don’t run them on the dependencies. This is the option that most tasks probably need. An example is the test task, it should test only the seeders, no need to test the dependencies.\n *\n * Again, the distinction between seedersCapsules and originalSeedersCapsules is relevant for build-pipeline only. For tag-pipeline and snap-pipeline, these two are the same. You can see for example that Publisher task runs on seedersCapsules and that’s fine, it won’t be running on dependencies unexpectedly, only on the components it’s now tagging.\n */",
-            "comment": "collection of isolated components (capsules).\nnormally, \"seeders\" are the components that this network was created for.\n\"graphCapsules\" is the graph created from the seeders and it includes also the dependencies.\n\nhowever, during \"bit build\"/\"bit tag\"/\"bit snap\", things are more complex because there is one more variable in the\npicture, which is the \"env\". the Network is created per env.\nin practice, for \"build-task\", a task is called per env, and the network passed to the task is relevant to that env.\nthe \"originalSeeders\" are the ones the network was created for, but only for this env.\nthe \"seeders\" are similar to the \"graphCapsules\" above, which contains also the dependencies, but only for this env.\nthe \"graphCapsules\" is the entire graph, including capsules from other envs.\n\nfor example:\ncomp1 depends on comp2. comp1 env is \"react\". comp2 env is \"aspect\".\n\nwhen the user is running \"bit build comp1\", two `Network` instances will be created with the following:\nNetwork for \"react\" env:  originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\nNetwork for \"aspect\" env: originalSeeders: [], seeders: ['comp2'], graphCapsules: ['comp2'].\n\non the other hand, when the user is running \"bit capsule create comp1\", only one `Network` instance is created:\nNetwork: originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\n\n(as a side note, another implementation was attempt to have the \"seeders\" as the original-seeders for build,\nhowever, it's failed. see https://github.com/teambit/bit/pull/5407 for more details).\n\n\nA more detailed explanation about the \"seeders\" vs \"originalSeeders\" vs \"graphCapsules\" is provided below:\nan example: comp1 -> comp2 -> comp3 (as in comp1 uses comp2, comp2 uses comp3).\nI changed only comp2.\nFrom comp2 perspective, comp1 is a “dependent”, comp3 is a “dependency”.\n\nWhen I run bit build with no args, it finds only one modified component: comp2, however, it doesn’t stop here. It also look for the dependents, in this case, comp1. So the seeders of this bit-build command are two: “comp1” and “comp2\".\nThe reason why the dependents are included is because you modified comp2, it’s possible you broke comp1. We want to build comp1 as well to make sure it’s still okay.\n(btw, bit test command also include dependents when it provided with no args).\n\nKeep in mind that also bit tag normally runs on the dependents as well (when it runs the build pipeline), because these are the “auto-tag”.\nWith these two seeders it builds the graph. The graph calculates all the dependencies of the given seeders recursively. Eventually, it puts them in an instance of Network class.\nIn our case, if all components use the same env, the Network consist of:\nseedersCapsules:          [comp1, comp2]\noriginalSeedersCapsules:  [comp1, comp2]\ngraphCapsules:            [comp1, comp2, comp3].\n\nIt gets more complex when multiple envs involved.\nImagine that comp1 uses env1, comp2 uses env2 and comp3 uses env3.\nBecause bit build runs the tasks per env, it needs to create 3 networks. Each per env.\nThe “seeders” refer to the seeders of the same env and includes only components from the same env.\nThe “originalSeeders” refer to the ones that originally started the build command and are from the same env.\nNetwork1:\nseedersCapsules:          [comp1]\noriginalSeedersCapsules:  [comp1]\ngraphCapsules:            [comp1, comp2, comp3].\nNetwork2:\nseedersCapsules:          [comp2]\noriginalSeedersCapsules:  [comp2]\ngraphCapsules:            [comp2, comp3].\nNetwork3:\nseedersCapsules:          [comp3]\noriginalSeedersCapsules:  []\ngraphCapsules:            [comp3].\nAs you can see, in network3, the originalSeeders is empty, because comp3 wasn’t part of the original seeders.\nThese 3 networks are created for build-pipeline. This pipeline asks for all components in the graph and then create the network per env.\nSnap/Tag pipelines are different. They ask only for the components about to tag/snap, which are the original-seeders, and create the network per env. For them, we end up with 2 network instances only. network1 and network2. Also, the seedersCapsules and originalSeedersCapsules are the same because we create the network instances out of the seeders only, without the dependencies.\nA build-task provides context with a network instance to the execute() method. (it also provide Component[] which are the “seeders”. not “originalSeeders”).\n\nEach build-task can decide on what components to operate. It has 3 options:\nrun on graphCapsules. If you do that, you risk running your task multiple times on the same components. In the example above, a task of build-pipeline, will run 3 times on comp3, because this component is part of the graphCapsules in each one of the network instance. So this is probably not recommended for most tasks.\nrun on seedersCapsules. With this option you make sure that your task is running for each one of the capsules and it runs only once. This is good for example for the compiler task. It needs to make sure all capsules are built. Otherwise, if it’s running only on originalSeedersCapsules, the comp3 won’t be compiled, the dists will be missing and comp2 won’t be able to run its tests.\nrun on originalSeedersCapsules . With this option you ensure that your task runs only on the ids you started with and you don’t run them on the dependencies. This is the option that most tasks probably need. An example is the test task, it should test only the seeders, no need to test the dependencies.\n\nAgain, the distinction between seedersCapsules and originalSeedersCapsules is relevant for build-pipeline only. For tag-pipeline and snap-pipeline, these two are the same. You can see for example that Publisher task runs on seedersCapsules and that’s fine, it won’t be running on dependencies unexpectedly, only on the components it’s now tagging."
+            "comment": "collection of isolated components (capsules).\nnormally, \"seeders\" are the components that this network was created for.\n\"graphCapsules\" is the graph created from the seeders and it includes also the dependencies.\n\nhowever, during \"bit build\"/\"bit tag\"/\"bit snap\", things are more complex because there is one more variable in the\npicture, which is the \"env\". the Network is created per env.\nin practice, for \"build-task\", a task is called per env, and the network passed to the task is relevant to that env.\nthe \"originalSeeders\" are the ones the network was created for, but only for this env.\nthe \"seeders\" are similar to the \"graphCapsules\" above, which contains also the dependencies, but only for this env.\nthe \"graphCapsules\" is the entire graph, including capsules from other envs.\n\nfor example:\ncomp1 depends on comp2. comp1 env is \"react\". comp2 env is \"aspect\".\n\nwhen the user is running \"bit build comp1\", two `Network` instances will be created with the following:\nNetwork for \"react\" env:  originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\nNetwork for \"aspect\" env: originalSeeders: [], seeders: ['comp2'], graphCapsules: ['comp2'].\n\non the other hand, when the user is running \"bit capsule create comp1\", only one `Network` instance is created:\nNetwork: originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\n\n(as a side note, another implementation was attempt to have the \"seeders\" as the original-seeders for build,\nhowever, it's failed. see https://github.com/teambit/bit/pull/5407 for more details).\n\n\nA more detailed explanation about the \"seeders\" vs \"originalSeeders\" vs \"graphCapsules\" is provided below:\nan example: comp1 -> comp2 -> comp3 (as in comp1 uses comp2, comp2 uses comp3).\nI changed only comp2.\nFrom comp2 perspective, comp1 is a “dependent”, comp3 is a “dependency”.\n\nWhen I run bit build with no args, it finds only one modified component: comp2, however, it doesn’t stop here. It also look for the dependents, in this case, comp1. So the seeders of this bit-build command are two: “comp1” and “comp2\".\nThe reason why the dependents are included is because you modified comp2, it’s possible you broke comp1. We want to build comp1 as well to make sure it’s still okay.\n(btw, bit test command also include dependents when it provided with no args).\n\nKeep in mind that also bit tag normally runs on the dependents as well (when it runs the build pipeline), because these are the “auto-tag”.\nWith these two seeders it builds the graph. The graph calculates all the dependencies of the given seeders recursively. Eventually, it puts them in an instance of Network class.\nIn our case, if all components use the same env, the Network consist of:\nseedersCapsules:          [comp1, comp2]\noriginalSeedersCapsules:  [comp1, comp2]\ngraphCapsules:            [comp1, comp2, comp3].\n\nIt gets more complex when multiple envs involved.\nImagine that comp1 uses env1, comp2 uses env2 and comp3 uses env3.\nBecause bit build runs the tasks per env, it needs to create 3 networks. Each per env.\nThe “seeders” refer to the seeders of the same env and includes only components from the same env.\nThe “originalSeeders” refer to the ones that originally started the build command and are from the same env.\nNetwork1:\nseedersCapsules:          [comp1]\noriginalSeedersCapsules:  [comp1]\ngraphCapsules:            [comp1, comp2, comp3].\nNetwork2:\nseedersCapsules:          [comp2]\noriginalSeedersCapsules:  [comp2]\ngraphCapsules:            [comp2, comp3].\nNetwork3:\nseedersCapsules:          [comp3]\noriginalSeedersCapsules:  []\ngraphCapsules:            [comp3].\nAs you can see, in network3, the originalSeeders is empty, because comp3 wasn’t part of the original seeders.\nThese 3 networks are created for build-pipeline. This pipeline asks for all components in the graph and then create the network per env.\nSnap/Tag pipelines are different. They ask only for the components about to tag/snap, which are the original-seeders, and create the network per env. For them, we end up with 2 network instances only. network1 and network2. Also, the seedersCapsules and originalSeedersCapsules are the same because we create the network instances out of the seeders only, without the dependencies.\nA build-task provides context with a network instance to the execute() method. (it also provide Component[] which are the “seeders”. not “originalSeeders”).\n\nEach build-task can decide on what components to operate. It has 3 options:\nrun on graphCapsules. If you do that, you risk running your task multiple times on the same components. In the example above, a task of build-pipeline, will run 3 times on comp3, because this component is part of the graphCapsules in each one of the network instance. So this is probably not recommended for most tasks.\nrun on seedersCapsules. With this option you make sure that your task is running for each one of the capsules and it runs only once. This is good for example for the compiler task. It needs to make sure all capsules are built. Otherwise, if it’s running only on originalSeedersCapsules, the comp3 won’t be compiled, the dists will be missing and comp2 won’t be able to run its tests.\nrun on originalSeedersCapsules . With this option you ensure that your task runs only on the ids you started with and you don’t run them on the dependencies. This is the option that most tasks probably need. An example is the test task, it should test only the seeders, no need to test the dependencies.\n\nAgain, the distinction between seedersCapsules and originalSeedersCapsules is relevant for build-pipeline only. For tag-pipeline and snap-pipeline, these two are the same. You can see for example that Publisher task runs on seedersCapsules and that’s fine, it won’t be running on dependencies unexpectedly, only on the components it’s now tagging.",
+            "tags": []
           },
           "signature": "class Network",
           "name": "Network",
@@ -272,7 +273,8 @@
                   "character": 3
                 },
                 "raw": "/**\n   * some of the capsules (non-modified) are written already with the dists files, so no need to re-compile them.\n   * this method helps optimizing compilers that are running on the capsules.\n   */",
-                "comment": "some of the capsules (non-modified) are written already with the dists files, so no need to re-compile them.\nthis method helps optimizing compilers that are running on the capsules."
+                "comment": "some of the capsules (non-modified) are written already with the dists files, so no need to re-compile them.\nthis method helps optimizing compilers that are running on the capsules.",
+                "tags": []
               },
               "signature": "(method) Network.getCapsulesToCompile(): Promise<CapsuleList>",
               "name": "getCapsulesToCompile",
@@ -1241,7 +1243,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -1964,6 +1966,7 @@
                   "character": 3
                 },
                 "raw": "/**\n   * @todo: fix.\n   * it skips the capsule fs because for some reason `capsule.fs.promises.readdir` doesn't work\n   * the same as `capsule.fs.readdir` and it doesn't have the capsule dir as pwd.\n   *\n   * returns the paths inside the capsule\n   */",
+                "comment": "",
                 "tags": [
                   {
                     "__schema": "TagSchema",
@@ -2469,7 +2472,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -2755,7 +2758,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -2784,7 +2787,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -3530,6 +3533,7 @@
                   "character": 3
                 },
                 "raw": "/**\n   *\n   * @param originalCapsule the capsule that contains the original component\n   * @param newBaseDir relative path. (it will be saved inside `this.getRootDirOfAllCapsules()`. the final path of the capsule will be getRootDirOfAllCapsules() + newBaseDir + filenameify(component.id))\n   * @returns a new capsule with the same content of the original capsule but with a new baseDir and all packages\n   * installed in the newBaseDir.\n   */",
+                "comment": "",
                 "tags": [
                   {
                     "__schema": "PropertyLikeTagSchema",
@@ -3747,6 +3751,7 @@
                   "character": 3
                 },
                 "raw": "/** @deprecated use the new function signature with an object parameter instead */",
+                "comment": "",
                 "tags": [
                   {
                     "__schema": "TagSchema",
@@ -4289,7 +4294,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * absolute path to put all the capsules dirs inside.\n   */",
-                      "comment": "absolute path to put all the capsules dirs inside."
+                      "comment": "absolute path to put all the capsules dirs inside.",
+                      "tags": []
                     },
                     "signature": "(property) rootBaseDir?: string | undefined",
                     "name": "rootBaseDir",
@@ -4319,7 +4325,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * the capsule root-dir based on a *hash* of this baseDir, not on the baseDir itself.\n   * A folder with this hash as its name will be created in the rootBaseDir\n   * By default this value will be the host path\n   */",
-                      "comment": "the capsule root-dir based on a *hash* of this baseDir, not on the baseDir itself.\nA folder with this hash as its name will be created in the rootBaseDir\nBy default this value will be the host path"
+                      "comment": "the capsule root-dir based on a *hash* of this baseDir, not on the baseDir itself.\nA folder with this hash as its name will be created in the rootBaseDir\nBy default this value will be the host path",
+                      "tags": []
                     },
                     "signature": "(property) baseDir?: string | undefined",
                     "name": "baseDir",
@@ -4349,7 +4356,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Whether to use hash function (of base dir) as capsules root dir name\n   */",
-                      "comment": "Whether to use hash function (of base dir) as capsules root dir name"
+                      "comment": "Whether to use hash function (of base dir) as capsules root dir name",
+                      "tags": []
                     },
                     "signature": "(property) useHash?: boolean | undefined",
                     "name": "useHash",
@@ -4379,7 +4387,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * create a new capsule with a random string attached to the path suffix\n   */",
-                      "comment": "create a new capsule with a random string attached to the path suffix"
+                      "comment": "create a new capsule with a random string attached to the path suffix",
+                      "tags": []
                     },
                     "signature": "(property) alwaysNew?: boolean | undefined",
                     "name": "alwaysNew",
@@ -4409,7 +4418,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * If this is true -\n   * the isolator will check if there are missing capsules in the base dir\n   * if yes, it will create the capsule in a special dir inside a dir with the current date (without time)\n   * then inside that dir, it will create a dir with a random hash\n   * at the end of the process it will move missing capsules from the temp dir to the base dir so they can be used in\n   * the next iteration\n   */",
-                      "comment": "If this is true -\nthe isolator will check if there are missing capsules in the base dir\nif yes, it will create the capsule in a special dir inside a dir with the current date (without time)\nthen inside that dir, it will create a dir with a random hash\nat the end of the process it will move missing capsules from the temp dir to the base dir so they can be used in\nthe next iteration"
+                      "comment": "If this is true -\nthe isolator will check if there are missing capsules in the base dir\nif yes, it will create the capsule in a special dir inside a dir with the current date (without time)\nthen inside that dir, it will create a dir with a random hash\nat the end of the process it will move missing capsules from the temp dir to the base dir so they can be used in\nthe next iteration",
+                      "tags": []
                     },
                     "signature": "(property) useDatedDirs?: boolean | undefined",
                     "name": "useDatedDirs",
@@ -4439,7 +4449,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * If this is true -\n   * the isolator will do few things:\n   * 1. in the end of the process it will only move the lock file (pnpm-lock.yaml) into the capsule cache\n   * 2. in the beginning of the process it will check if there is a lock file in the capsule cache, if yes it will move\n   * it to the temp dated dir\n   * 3. it will write env's file into the dated dir (as it only contain the lock file)\n   * 4. it will run install in the dated dir (as there is no node_modules there yet)\n   */",
-                      "comment": "If this is true -\nthe isolator will do few things:\n1. in the end of the process it will only move the lock file (pnpm-lock.yaml) into the capsule cache\n2. in the beginning of the process it will check if there is a lock file in the capsule cache, if yes it will move\nit to the temp dated dir\n3. it will write env's file into the dated dir (as it only contain the lock file)\n4. it will run install in the dated dir (as there is no node_modules there yet)"
+                      "comment": "If this is true -\nthe isolator will do few things:\n1. in the end of the process it will only move the lock file (pnpm-lock.yaml) into the capsule cache\n2. in the beginning of the process it will check if there is a lock file in the capsule cache, if yes it will move\nit to the temp dated dir\n3. it will write env's file into the dated dir (as it only contain the lock file)\n4. it will run install in the dated dir (as there is no node_modules there yet)",
+                      "tags": []
                     },
                     "signature": "(property) cacheLockFileOnly?: boolean | undefined",
                     "name": "cacheLockFileOnly",
@@ -4469,7 +4480,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * If set, along with useDatedDirs, then we will use the same hash dir for all capsules created with the same\n   * datedDirId\n   */",
-                      "comment": "If set, along with useDatedDirs, then we will use the same hash dir for all capsules created with the same\ndatedDirId"
+                      "comment": "If set, along with useDatedDirs, then we will use the same hash dir for all capsules created with the same\ndatedDirId",
+                      "tags": []
                     },
                     "signature": "(property) datedDirId?: string | undefined",
                     "name": "datedDirId",
@@ -4499,7 +4511,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * installation options\n   */",
-                      "comment": "installation options"
+                      "comment": "installation options",
+                      "tags": []
                     },
                     "signature": "(property) installOptions?: IsolateComponentsInstallOptions | undefined",
                     "name": "installOptions",
@@ -4554,7 +4567,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * delete the capsule rootDir first. it makes sure that the isolation process starts fresh with\n   * no previous capsules. for build and tag this is true.\n   */",
-                      "comment": "delete the capsule rootDir first. it makes sure that the isolation process starts fresh with\nno previous capsules. for build and tag this is true."
+                      "comment": "delete the capsule rootDir first. it makes sure that the isolation process starts fresh with\nno previous capsules. for build and tag this is true.",
+                      "tags": []
                     },
                     "signature": "(property) emptyRootDir?: boolean | undefined",
                     "name": "emptyRootDir",
@@ -4584,7 +4598,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * skip the reproduction of the capsule in case it exists.\n   */",
-                      "comment": "skip the reproduction of the capsule in case it exists."
+                      "comment": "skip the reproduction of the capsule in case it exists.",
+                      "tags": []
                     },
                     "signature": "(property) skipIfExists?: boolean | undefined",
                     "name": "skipIfExists",
@@ -4614,7 +4629,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * get existing capsule without doing any changes, no writes, no installations.\n   */",
-                      "comment": "get existing capsule without doing any changes, no writes, no installations."
+                      "comment": "get existing capsule without doing any changes, no writes, no installations.",
+                      "tags": []
                     },
                     "signature": "(property) getExistingAsIs?: boolean | undefined",
                     "name": "getExistingAsIs",
@@ -4644,7 +4660,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * place the package-manager cache on the capsule-root\n   */",
-                      "comment": "place the package-manager cache on the capsule-root"
+                      "comment": "place the package-manager cache on the capsule-root",
+                      "tags": []
                     },
                     "signature": "(property) cachePackagesOnCapsulesRoot?: boolean | undefined",
                     "name": "cachePackagesOnCapsulesRoot",
@@ -4674,7 +4691,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * do not build graph with all dependencies. isolate the seeders only.\n   */",
-                      "comment": "do not build graph with all dependencies. isolate the seeders only."
+                      "comment": "do not build graph with all dependencies. isolate the seeders only.",
+                      "tags": []
                     },
                     "signature": "(property) seedersOnly?: boolean | undefined",
                     "name": "seedersOnly",
@@ -4704,7 +4722,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * relevant for tagging from scope, where we tag an existing snap without any code-changes.\n   * the idea is to have all build artifacts from the previous snap and run deploy pipeline on top of it.\n   */",
-                      "comment": "relevant for tagging from scope, where we tag an existing snap without any code-changes.\nthe idea is to have all build artifacts from the previous snap and run deploy pipeline on top of it."
+                      "comment": "relevant for tagging from scope, where we tag an existing snap without any code-changes.\nthe idea is to have all build artifacts from the previous snap and run deploy pipeline on top of it.",
+                      "tags": []
                     },
                     "signature": "(property) populateArtifactsFrom?: ComponentID[] | undefined",
                     "name": "populateArtifactsFrom",
@@ -4747,7 +4766,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Force specific host to get the component from.\n   */",
-                      "comment": "Force specific host to get the component from."
+                      "comment": "Force specific host to get the component from.",
+                      "tags": []
                     },
                     "signature": "(property) host?: ComponentFactory | undefined",
                     "name": "host",
@@ -4781,7 +4801,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Use specific package manager for the isolation process (override the package manager from the dep resolver config)\n   */",
-                      "comment": "Use specific package manager for the isolation process (override the package manager from the dep resolver config)"
+                      "comment": "Use specific package manager for the isolation process (override the package manager from the dep resolver config)",
+                      "tags": []
                     },
                     "signature": "(property) packageManager?: string | undefined",
                     "name": "packageManager",
@@ -4811,7 +4832,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Use specific node linker for the isolation process (override the package manager from the dep resolver config)\n   */",
-                      "comment": "Use specific node linker for the isolation process (override the package manager from the dep resolver config)"
+                      "comment": "Use specific node linker for the isolation process (override the package manager from the dep resolver config)",
+                      "tags": []
                     },
                     "signature": "(property) nodeLinker?: NodeLinker | undefined",
                     "name": "nodeLinker",
@@ -4845,7 +4867,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Dir where to read the package manager config from\n   * usually used when running package manager in the capsules dir to use the config\n   * from the workspace dir\n   */",
-                      "comment": "Dir where to read the package manager config from\nusually used when running package manager in the capsules dir to use the config\nfrom the workspace dir"
+                      "comment": "Dir where to read the package manager config from\nusually used when running package manager in the capsules dir to use the config\nfrom the workspace dir",
+                      "tags": []
                     },
                     "signature": "(property) packageManagerConfigRootDir?: string | undefined",
                     "name": "packageManagerConfigRootDir",
@@ -4896,7 +4919,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Root dir of capsulse cache (used mostly to copy lock file if used with cache lock file only option)\n   */",
-                      "comment": "Root dir of capsulse cache (used mostly to copy lock file if used with cache lock file only option)"
+                      "comment": "Root dir of capsulse cache (used mostly to copy lock file if used with cache lock file only option)",
+                      "tags": []
                     },
                     "signature": "(property) cacheCapsulesDir?: string | undefined",
                     "name": "cacheCapsulesDir",
@@ -5474,7 +5498,8 @@
                   "character": 3
                 },
                 "raw": "/**\n   * determines whether or not a capsule can theoretically use the dists saved in the last snap, rather than re-compile them.\n   * practically, this optimization is used for components that have typescript as their compiler.\n   */",
-                "comment": "determines whether or not a capsule can theoretically use the dists saved in the last snap, rather than re-compile them.\npractically, this optimization is used for components that have typescript as their compiler."
+                "comment": "determines whether or not a capsule can theoretically use the dists saved in the last snap, rather than re-compile them.\npractically, this optimization is used for components that have typescript as their compiler.",
+                "tags": []
               },
               "signature": "(method) CapsuleList.capsuleUsePreviouslySavedDists(component: Component): Promise<boolean>",
               "name": "capsuleUsePreviouslySavedDists",
@@ -5562,7 +5587,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -5600,7 +5625,8 @@
               "character": 1
             },
             "raw": "/**\n * collection of isolated components (capsules).\n * normally, \"seeders\" are the components that this network was created for.\n * \"graphCapsules\" is the graph created from the seeders and it includes also the dependencies.\n *\n * however, during \"bit build\"/\"bit tag\"/\"bit snap\", things are more complex because there is one more variable in the\n * picture, which is the \"env\". the Network is created per env.\n * in practice, for \"build-task\", a task is called per env, and the network passed to the task is relevant to that env.\n * the \"originalSeeders\" are the ones the network was created for, but only for this env.\n * the \"seeders\" are similar to the \"graphCapsules\" above, which contains also the dependencies, but only for this env.\n * the \"graphCapsules\" is the entire graph, including capsules from other envs.\n *\n * for example:\n * comp1 depends on comp2. comp1 env is \"react\". comp2 env is \"aspect\".\n *\n * when the user is running \"bit build comp1\", two `Network` instances will be created with the following:\n * Network for \"react\" env:  originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\n * Network for \"aspect\" env: originalSeeders: [], seeders: ['comp2'], graphCapsules: ['comp2'].\n *\n * on the other hand, when the user is running \"bit capsule create comp1\", only one `Network` instance is created:\n * Network: originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\n *\n * (as a side note, another implementation was attempt to have the \"seeders\" as the original-seeders for build,\n * however, it's failed. see https://github.com/teambit/bit/pull/5407 for more details).\n *\n *\n * A more detailed explanation about the \"seeders\" vs \"originalSeeders\" vs \"graphCapsules\" is provided below:\n * an example: comp1 -> comp2 -> comp3 (as in comp1 uses comp2, comp2 uses comp3).\n * I changed only comp2.\n * From comp2 perspective, comp1 is a “dependent”, comp3 is a “dependency”.\n *\n * When I run bit build with no args, it finds only one modified component: comp2, however, it doesn’t stop here. It also look for the dependents, in this case, comp1. So the seeders of this bit-build command are two: “comp1” and “comp2\".\n * The reason why the dependents are included is because you modified comp2, it’s possible you broke comp1. We want to build comp1 as well to make sure it’s still okay.\n * (btw, bit test command also include dependents when it provided with no args).\n *\n * Keep in mind that also bit tag normally runs on the dependents as well (when it runs the build pipeline), because these are the “auto-tag”.\n * With these two seeders it builds the graph. The graph calculates all the dependencies of the given seeders recursively. Eventually, it puts them in an instance of Network class.\n * In our case, if all components use the same env, the Network consist of:\n * seedersCapsules:          [comp1, comp2]\n * originalSeedersCapsules:  [comp1, comp2]\n * graphCapsules:            [comp1, comp2, comp3].\n *\n * It gets more complex when multiple envs involved.\n * Imagine that comp1 uses env1, comp2 uses env2 and comp3 uses env3.\n * Because bit build runs the tasks per env, it needs to create 3 networks. Each per env.\n * The “seeders” refer to the seeders of the same env and includes only components from the same env.\n * The “originalSeeders” refer to the ones that originally started the build command and are from the same env.\n * Network1:\n * seedersCapsules:          [comp1]\n * originalSeedersCapsules:  [comp1]\n * graphCapsules:            [comp1, comp2, comp3].\n * Network2:\n * seedersCapsules:          [comp2]\n * originalSeedersCapsules:  [comp2]\n * graphCapsules:            [comp2, comp3].\n * Network3:\n * seedersCapsules:          [comp3]\n * originalSeedersCapsules:  []\n * graphCapsules:            [comp3].\n * As you can see, in network3, the originalSeeders is empty, because comp3 wasn’t part of the original seeders.\n * These 3 networks are created for build-pipeline. This pipeline asks for all components in the graph and then create the network per env.\n * Snap/Tag pipelines are different. They ask only for the components about to tag/snap, which are the original-seeders, and create the network per env. For them, we end up with 2 network instances only. network1 and network2. Also, the seedersCapsules and originalSeedersCapsules are the same because we create the network instances out of the seeders only, without the dependencies.\n * A build-task provides context with a network instance to the execute() method. (it also provide Component[] which are the “seeders”. not “originalSeeders”).\n *\n * Each build-task can decide on what components to operate. It has 3 options:\n * run on graphCapsules. If you do that, you risk running your task multiple times on the same components. In the example above, a task of build-pipeline, will run 3 times on comp3, because this component is part of the graphCapsules in each one of the network instance. So this is probably not recommended for most tasks.\n * run on seedersCapsules. With this option you make sure that your task is running for each one of the capsules and it runs only once. This is good for example for the compiler task. It needs to make sure all capsules are built. Otherwise, if it’s running only on originalSeedersCapsules, the comp3 won’t be compiled, the dists will be missing and comp2 won’t be able to run its tests.\n * run on originalSeedersCapsules . With this option you ensure that your task runs only on the ids you started with and you don’t run them on the dependencies. This is the option that most tasks probably need. An example is the test task, it should test only the seeders, no need to test the dependencies.\n *\n * Again, the distinction between seedersCapsules and originalSeedersCapsules is relevant for build-pipeline only. For tag-pipeline and snap-pipeline, these two are the same. You can see for example that Publisher task runs on seedersCapsules and that’s fine, it won’t be running on dependencies unexpectedly, only on the components it’s now tagging.\n */",
-            "comment": "collection of isolated components (capsules).\nnormally, \"seeders\" are the components that this network was created for.\n\"graphCapsules\" is the graph created from the seeders and it includes also the dependencies.\n\nhowever, during \"bit build\"/\"bit tag\"/\"bit snap\", things are more complex because there is one more variable in the\npicture, which is the \"env\". the Network is created per env.\nin practice, for \"build-task\", a task is called per env, and the network passed to the task is relevant to that env.\nthe \"originalSeeders\" are the ones the network was created for, but only for this env.\nthe \"seeders\" are similar to the \"graphCapsules\" above, which contains also the dependencies, but only for this env.\nthe \"graphCapsules\" is the entire graph, including capsules from other envs.\n\nfor example:\ncomp1 depends on comp2. comp1 env is \"react\". comp2 env is \"aspect\".\n\nwhen the user is running \"bit build comp1\", two `Network` instances will be created with the following:\nNetwork for \"react\" env:  originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\nNetwork for \"aspect\" env: originalSeeders: [], seeders: ['comp2'], graphCapsules: ['comp2'].\n\non the other hand, when the user is running \"bit capsule create comp1\", only one `Network` instance is created:\nNetwork: originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\n\n(as a side note, another implementation was attempt to have the \"seeders\" as the original-seeders for build,\nhowever, it's failed. see https://github.com/teambit/bit/pull/5407 for more details).\n\n\nA more detailed explanation about the \"seeders\" vs \"originalSeeders\" vs \"graphCapsules\" is provided below:\nan example: comp1 -> comp2 -> comp3 (as in comp1 uses comp2, comp2 uses comp3).\nI changed only comp2.\nFrom comp2 perspective, comp1 is a “dependent”, comp3 is a “dependency”.\n\nWhen I run bit build with no args, it finds only one modified component: comp2, however, it doesn’t stop here. It also look for the dependents, in this case, comp1. So the seeders of this bit-build command are two: “comp1” and “comp2\".\nThe reason why the dependents are included is because you modified comp2, it’s possible you broke comp1. We want to build comp1 as well to make sure it’s still okay.\n(btw, bit test command also include dependents when it provided with no args).\n\nKeep in mind that also bit tag normally runs on the dependents as well (when it runs the build pipeline), because these are the “auto-tag”.\nWith these two seeders it builds the graph. The graph calculates all the dependencies of the given seeders recursively. Eventually, it puts them in an instance of Network class.\nIn our case, if all components use the same env, the Network consist of:\nseedersCapsules:          [comp1, comp2]\noriginalSeedersCapsules:  [comp1, comp2]\ngraphCapsules:            [comp1, comp2, comp3].\n\nIt gets more complex when multiple envs involved.\nImagine that comp1 uses env1, comp2 uses env2 and comp3 uses env3.\nBecause bit build runs the tasks per env, it needs to create 3 networks. Each per env.\nThe “seeders” refer to the seeders of the same env and includes only components from the same env.\nThe “originalSeeders” refer to the ones that originally started the build command and are from the same env.\nNetwork1:\nseedersCapsules:          [comp1]\noriginalSeedersCapsules:  [comp1]\ngraphCapsules:            [comp1, comp2, comp3].\nNetwork2:\nseedersCapsules:          [comp2]\noriginalSeedersCapsules:  [comp2]\ngraphCapsules:            [comp2, comp3].\nNetwork3:\nseedersCapsules:          [comp3]\noriginalSeedersCapsules:  []\ngraphCapsules:            [comp3].\nAs you can see, in network3, the originalSeeders is empty, because comp3 wasn’t part of the original seeders.\nThese 3 networks are created for build-pipeline. This pipeline asks for all components in the graph and then create the network per env.\nSnap/Tag pipelines are different. They ask only for the components about to tag/snap, which are the original-seeders, and create the network per env. For them, we end up with 2 network instances only. network1 and network2. Also, the seedersCapsules and originalSeedersCapsules are the same because we create the network instances out of the seeders only, without the dependencies.\nA build-task provides context with a network instance to the execute() method. (it also provide Component[] which are the “seeders”. not “originalSeeders”).\n\nEach build-task can decide on what components to operate. It has 3 options:\nrun on graphCapsules. If you do that, you risk running your task multiple times on the same components. In the example above, a task of build-pipeline, will run 3 times on comp3, because this component is part of the graphCapsules in each one of the network instance. So this is probably not recommended for most tasks.\nrun on seedersCapsules. With this option you make sure that your task is running for each one of the capsules and it runs only once. This is good for example for the compiler task. It needs to make sure all capsules are built. Otherwise, if it’s running only on originalSeedersCapsules, the comp3 won’t be compiled, the dists will be missing and comp2 won’t be able to run its tests.\nrun on originalSeedersCapsules . With this option you ensure that your task runs only on the ids you started with and you don’t run them on the dependencies. This is the option that most tasks probably need. An example is the test task, it should test only the seeders, no need to test the dependencies.\n\nAgain, the distinction between seedersCapsules and originalSeedersCapsules is relevant for build-pipeline only. For tag-pipeline and snap-pipeline, these two are the same. You can see for example that Publisher task runs on seedersCapsules and that’s fine, it won’t be running on dependencies unexpectedly, only on the components it’s now tagging."
+            "comment": "collection of isolated components (capsules).\nnormally, \"seeders\" are the components that this network was created for.\n\"graphCapsules\" is the graph created from the seeders and it includes also the dependencies.\n\nhowever, during \"bit build\"/\"bit tag\"/\"bit snap\", things are more complex because there is one more variable in the\npicture, which is the \"env\". the Network is created per env.\nin practice, for \"build-task\", a task is called per env, and the network passed to the task is relevant to that env.\nthe \"originalSeeders\" are the ones the network was created for, but only for this env.\nthe \"seeders\" are similar to the \"graphCapsules\" above, which contains also the dependencies, but only for this env.\nthe \"graphCapsules\" is the entire graph, including capsules from other envs.\n\nfor example:\ncomp1 depends on comp2. comp1 env is \"react\". comp2 env is \"aspect\".\n\nwhen the user is running \"bit build comp1\", two `Network` instances will be created with the following:\nNetwork for \"react\" env:  originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\nNetwork for \"aspect\" env: originalSeeders: [], seeders: ['comp2'], graphCapsules: ['comp2'].\n\non the other hand, when the user is running \"bit capsule create comp1\", only one `Network` instance is created:\nNetwork: originalSeeders: ['comp1'], seeders: ['comp1'], graphCapsules: ['comp1', 'comp2'].\n\n(as a side note, another implementation was attempt to have the \"seeders\" as the original-seeders for build,\nhowever, it's failed. see https://github.com/teambit/bit/pull/5407 for more details).\n\n\nA more detailed explanation about the \"seeders\" vs \"originalSeeders\" vs \"graphCapsules\" is provided below:\nan example: comp1 -> comp2 -> comp3 (as in comp1 uses comp2, comp2 uses comp3).\nI changed only comp2.\nFrom comp2 perspective, comp1 is a “dependent”, comp3 is a “dependency”.\n\nWhen I run bit build with no args, it finds only one modified component: comp2, however, it doesn’t stop here. It also look for the dependents, in this case, comp1. So the seeders of this bit-build command are two: “comp1” and “comp2\".\nThe reason why the dependents are included is because you modified comp2, it’s possible you broke comp1. We want to build comp1 as well to make sure it’s still okay.\n(btw, bit test command also include dependents when it provided with no args).\n\nKeep in mind that also bit tag normally runs on the dependents as well (when it runs the build pipeline), because these are the “auto-tag”.\nWith these two seeders it builds the graph. The graph calculates all the dependencies of the given seeders recursively. Eventually, it puts them in an instance of Network class.\nIn our case, if all components use the same env, the Network consist of:\nseedersCapsules:          [comp1, comp2]\noriginalSeedersCapsules:  [comp1, comp2]\ngraphCapsules:            [comp1, comp2, comp3].\n\nIt gets more complex when multiple envs involved.\nImagine that comp1 uses env1, comp2 uses env2 and comp3 uses env3.\nBecause bit build runs the tasks per env, it needs to create 3 networks. Each per env.\nThe “seeders” refer to the seeders of the same env and includes only components from the same env.\nThe “originalSeeders” refer to the ones that originally started the build command and are from the same env.\nNetwork1:\nseedersCapsules:          [comp1]\noriginalSeedersCapsules:  [comp1]\ngraphCapsules:            [comp1, comp2, comp3].\nNetwork2:\nseedersCapsules:          [comp2]\noriginalSeedersCapsules:  [comp2]\ngraphCapsules:            [comp2, comp3].\nNetwork3:\nseedersCapsules:          [comp3]\noriginalSeedersCapsules:  []\ngraphCapsules:            [comp3].\nAs you can see, in network3, the originalSeeders is empty, because comp3 wasn’t part of the original seeders.\nThese 3 networks are created for build-pipeline. This pipeline asks for all components in the graph and then create the network per env.\nSnap/Tag pipelines are different. They ask only for the components about to tag/snap, which are the original-seeders, and create the network per env. For them, we end up with 2 network instances only. network1 and network2. Also, the seedersCapsules and originalSeedersCapsules are the same because we create the network instances out of the seeders only, without the dependencies.\nA build-task provides context with a network instance to the execute() method. (it also provide Component[] which are the “seeders”. not “originalSeeders”).\n\nEach build-task can decide on what components to operate. It has 3 options:\nrun on graphCapsules. If you do that, you risk running your task multiple times on the same components. In the example above, a task of build-pipeline, will run 3 times on comp3, because this component is part of the graphCapsules in each one of the network instance. So this is probably not recommended for most tasks.\nrun on seedersCapsules. With this option you make sure that your task is running for each one of the capsules and it runs only once. This is good for example for the compiler task. It needs to make sure all capsules are built. Otherwise, if it’s running only on originalSeedersCapsules, the comp3 won’t be compiled, the dists will be missing and comp2 won’t be able to run its tests.\nrun on originalSeedersCapsules . With this option you ensure that your task runs only on the ids you started with and you don’t run them on the dependencies. This is the option that most tasks probably need. An example is the test task, it should test only the seeders, no need to test the dependencies.\n\nAgain, the distinction between seedersCapsules and originalSeedersCapsules is relevant for build-pipeline only. For tag-pipeline and snap-pipeline, these two are the same. You can see for example that Publisher task runs on seedersCapsules and that’s fine, it won’t be running on dependencies unexpectedly, only on the components it’s now tagging.",
+            "tags": []
           },
           "signature": "class Network",
           "name": "Network",
@@ -5806,7 +5832,8 @@
                   "character": 3
                 },
                 "raw": "/**\n   * some of the capsules (non-modified) are written already with the dists files, so no need to re-compile them.\n   * this method helps optimizing compilers that are running on the capsules.\n   */",
-                "comment": "some of the capsules (non-modified) are written already with the dists files, so no need to re-compile them.\nthis method helps optimizing compilers that are running on the capsules."
+                "comment": "some of the capsules (non-modified) are written already with the dists files, so no need to re-compile them.\nthis method helps optimizing compilers that are running on the capsules.",
+                "tags": []
               },
               "signature": "(method) Network.getCapsulesToCompile(): Promise<CapsuleList>",
               "name": "getCapsulesToCompile",
@@ -6017,7 +6044,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -6078,7 +6105,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -6984,7 +7011,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -7742,6 +7769,7 @@
                   "character": 3
                 },
                 "raw": "/**\n   * @todo: fix.\n   * it skips the capsule fs because for some reason `capsule.fs.promises.readdir` doesn't work\n   * the same as `capsule.fs.readdir` and it doesn't have the capsule dir as pwd.\n   *\n   * returns the paths inside the capsule\n   */",
+                "comment": "",
                 "tags": [
                   {
                     "__schema": "TagSchema",
@@ -8247,7 +8275,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -8535,7 +8563,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -8564,7 +8592,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -8765,7 +8793,8 @@
               "character": 1
             },
             "raw": "/**\n * Context for the isolation process\n */",
-            "comment": "Context for the isolation process"
+            "comment": "Context for the isolation process",
+            "tags": []
           },
           "signature": "type IsolationContext = {\n    aspects?: boolean | undefined;\n    workspaceName?: string | undefined;\n}",
           "name": "IsolationContext",
@@ -8792,7 +8821,8 @@
                     "character": 3
                   },
                   "raw": "/**\n   * Whether the isolation done for aspects (as opposed to regular components)\n   */",
-                  "comment": "Whether the isolation done for aspects (as opposed to regular components)"
+                  "comment": "Whether the isolation done for aspects (as opposed to regular components)",
+                  "tags": []
                 },
                 "signature": "(property) aspects?: boolean | undefined",
                 "name": "aspects",
@@ -8822,7 +8852,8 @@
                     "character": 3
                   },
                   "raw": "/**\n   * Workspace name where the isolation starts from\n   */",
-                  "comment": "Workspace name where the isolation starts from"
+                  "comment": "Workspace name where the isolation starts from",
+                  "tags": []
                 },
                 "signature": "(property) workspaceName?: string | undefined",
                 "name": "workspaceName",
@@ -9090,7 +9121,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * absolute path to put all the capsules dirs inside.\n   */",
-                      "comment": "absolute path to put all the capsules dirs inside."
+                      "comment": "absolute path to put all the capsules dirs inside.",
+                      "tags": []
                     },
                     "signature": "(property) rootBaseDir?: string | undefined",
                     "name": "rootBaseDir",
@@ -9120,7 +9152,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * the capsule root-dir based on a *hash* of this baseDir, not on the baseDir itself.\n   * A folder with this hash as its name will be created in the rootBaseDir\n   * By default this value will be the host path\n   */",
-                      "comment": "the capsule root-dir based on a *hash* of this baseDir, not on the baseDir itself.\nA folder with this hash as its name will be created in the rootBaseDir\nBy default this value will be the host path"
+                      "comment": "the capsule root-dir based on a *hash* of this baseDir, not on the baseDir itself.\nA folder with this hash as its name will be created in the rootBaseDir\nBy default this value will be the host path",
+                      "tags": []
                     },
                     "signature": "(property) baseDir?: string | undefined",
                     "name": "baseDir",
@@ -9150,7 +9183,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Whether to use hash function (of base dir) as capsules root dir name\n   */",
-                      "comment": "Whether to use hash function (of base dir) as capsules root dir name"
+                      "comment": "Whether to use hash function (of base dir) as capsules root dir name",
+                      "tags": []
                     },
                     "signature": "(property) useHash?: boolean | undefined",
                     "name": "useHash",
@@ -9180,7 +9214,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * create a new capsule with a random string attached to the path suffix\n   */",
-                      "comment": "create a new capsule with a random string attached to the path suffix"
+                      "comment": "create a new capsule with a random string attached to the path suffix",
+                      "tags": []
                     },
                     "signature": "(property) alwaysNew?: boolean | undefined",
                     "name": "alwaysNew",
@@ -9210,7 +9245,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * If this is true -\n   * the isolator will check if there are missing capsules in the base dir\n   * if yes, it will create the capsule in a special dir inside a dir with the current date (without time)\n   * then inside that dir, it will create a dir with a random hash\n   * at the end of the process it will move missing capsules from the temp dir to the base dir so they can be used in\n   * the next iteration\n   */",
-                      "comment": "If this is true -\nthe isolator will check if there are missing capsules in the base dir\nif yes, it will create the capsule in a special dir inside a dir with the current date (without time)\nthen inside that dir, it will create a dir with a random hash\nat the end of the process it will move missing capsules from the temp dir to the base dir so they can be used in\nthe next iteration"
+                      "comment": "If this is true -\nthe isolator will check if there are missing capsules in the base dir\nif yes, it will create the capsule in a special dir inside a dir with the current date (without time)\nthen inside that dir, it will create a dir with a random hash\nat the end of the process it will move missing capsules from the temp dir to the base dir so they can be used in\nthe next iteration",
+                      "tags": []
                     },
                     "signature": "(property) useDatedDirs?: boolean | undefined",
                     "name": "useDatedDirs",
@@ -9240,7 +9276,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * If this is true -\n   * the isolator will do few things:\n   * 1. in the end of the process it will only move the lock file (pnpm-lock.yaml) into the capsule cache\n   * 2. in the beginning of the process it will check if there is a lock file in the capsule cache, if yes it will move\n   * it to the temp dated dir\n   * 3. it will write env's file into the dated dir (as it only contain the lock file)\n   * 4. it will run install in the dated dir (as there is no node_modules there yet)\n   */",
-                      "comment": "If this is true -\nthe isolator will do few things:\n1. in the end of the process it will only move the lock file (pnpm-lock.yaml) into the capsule cache\n2. in the beginning of the process it will check if there is a lock file in the capsule cache, if yes it will move\nit to the temp dated dir\n3. it will write env's file into the dated dir (as it only contain the lock file)\n4. it will run install in the dated dir (as there is no node_modules there yet)"
+                      "comment": "If this is true -\nthe isolator will do few things:\n1. in the end of the process it will only move the lock file (pnpm-lock.yaml) into the capsule cache\n2. in the beginning of the process it will check if there is a lock file in the capsule cache, if yes it will move\nit to the temp dated dir\n3. it will write env's file into the dated dir (as it only contain the lock file)\n4. it will run install in the dated dir (as there is no node_modules there yet)",
+                      "tags": []
                     },
                     "signature": "(property) cacheLockFileOnly?: boolean | undefined",
                     "name": "cacheLockFileOnly",
@@ -9270,7 +9307,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * If set, along with useDatedDirs, then we will use the same hash dir for all capsules created with the same\n   * datedDirId\n   */",
-                      "comment": "If set, along with useDatedDirs, then we will use the same hash dir for all capsules created with the same\ndatedDirId"
+                      "comment": "If set, along with useDatedDirs, then we will use the same hash dir for all capsules created with the same\ndatedDirId",
+                      "tags": []
                     },
                     "signature": "(property) datedDirId?: string | undefined",
                     "name": "datedDirId",
@@ -9300,7 +9338,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * installation options\n   */",
-                      "comment": "installation options"
+                      "comment": "installation options",
+                      "tags": []
                     },
                     "signature": "(property) installOptions?: IsolateComponentsInstallOptions | undefined",
                     "name": "installOptions",
@@ -9355,7 +9394,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * delete the capsule rootDir first. it makes sure that the isolation process starts fresh with\n   * no previous capsules. for build and tag this is true.\n   */",
-                      "comment": "delete the capsule rootDir first. it makes sure that the isolation process starts fresh with\nno previous capsules. for build and tag this is true."
+                      "comment": "delete the capsule rootDir first. it makes sure that the isolation process starts fresh with\nno previous capsules. for build and tag this is true.",
+                      "tags": []
                     },
                     "signature": "(property) emptyRootDir?: boolean | undefined",
                     "name": "emptyRootDir",
@@ -9385,7 +9425,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * skip the reproduction of the capsule in case it exists.\n   */",
-                      "comment": "skip the reproduction of the capsule in case it exists."
+                      "comment": "skip the reproduction of the capsule in case it exists.",
+                      "tags": []
                     },
                     "signature": "(property) skipIfExists?: boolean | undefined",
                     "name": "skipIfExists",
@@ -9415,7 +9456,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * get existing capsule without doing any changes, no writes, no installations.\n   */",
-                      "comment": "get existing capsule without doing any changes, no writes, no installations."
+                      "comment": "get existing capsule without doing any changes, no writes, no installations.",
+                      "tags": []
                     },
                     "signature": "(property) getExistingAsIs?: boolean | undefined",
                     "name": "getExistingAsIs",
@@ -9445,7 +9487,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * place the package-manager cache on the capsule-root\n   */",
-                      "comment": "place the package-manager cache on the capsule-root"
+                      "comment": "place the package-manager cache on the capsule-root",
+                      "tags": []
                     },
                     "signature": "(property) cachePackagesOnCapsulesRoot?: boolean | undefined",
                     "name": "cachePackagesOnCapsulesRoot",
@@ -9475,7 +9518,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * do not build graph with all dependencies. isolate the seeders only.\n   */",
-                      "comment": "do not build graph with all dependencies. isolate the seeders only."
+                      "comment": "do not build graph with all dependencies. isolate the seeders only.",
+                      "tags": []
                     },
                     "signature": "(property) seedersOnly?: boolean | undefined",
                     "name": "seedersOnly",
@@ -9505,7 +9549,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * relevant for tagging from scope, where we tag an existing snap without any code-changes.\n   * the idea is to have all build artifacts from the previous snap and run deploy pipeline on top of it.\n   */",
-                      "comment": "relevant for tagging from scope, where we tag an existing snap without any code-changes.\nthe idea is to have all build artifacts from the previous snap and run deploy pipeline on top of it."
+                      "comment": "relevant for tagging from scope, where we tag an existing snap without any code-changes.\nthe idea is to have all build artifacts from the previous snap and run deploy pipeline on top of it.",
+                      "tags": []
                     },
                     "signature": "(property) populateArtifactsFrom?: ComponentID[] | undefined",
                     "name": "populateArtifactsFrom",
@@ -9548,7 +9593,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Force specific host to get the component from.\n   */",
-                      "comment": "Force specific host to get the component from."
+                      "comment": "Force specific host to get the component from.",
+                      "tags": []
                     },
                     "signature": "(property) host?: ComponentFactory | undefined",
                     "name": "host",
@@ -9582,7 +9628,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Use specific package manager for the isolation process (override the package manager from the dep resolver config)\n   */",
-                      "comment": "Use specific package manager for the isolation process (override the package manager from the dep resolver config)"
+                      "comment": "Use specific package manager for the isolation process (override the package manager from the dep resolver config)",
+                      "tags": []
                     },
                     "signature": "(property) packageManager?: string | undefined",
                     "name": "packageManager",
@@ -9612,7 +9659,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Use specific node linker for the isolation process (override the package manager from the dep resolver config)\n   */",
-                      "comment": "Use specific node linker for the isolation process (override the package manager from the dep resolver config)"
+                      "comment": "Use specific node linker for the isolation process (override the package manager from the dep resolver config)",
+                      "tags": []
                     },
                     "signature": "(property) nodeLinker?: NodeLinker | undefined",
                     "name": "nodeLinker",
@@ -9646,7 +9694,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Dir where to read the package manager config from\n   * usually used when running package manager in the capsules dir to use the config\n   * from the workspace dir\n   */",
-                      "comment": "Dir where to read the package manager config from\nusually used when running package manager in the capsules dir to use the config\nfrom the workspace dir"
+                      "comment": "Dir where to read the package manager config from\nusually used when running package manager in the capsules dir to use the config\nfrom the workspace dir",
+                      "tags": []
                     },
                     "signature": "(property) packageManagerConfigRootDir?: string | undefined",
                     "name": "packageManagerConfigRootDir",
@@ -9697,7 +9746,8 @@
                         "character": 3
                       },
                       "raw": "/**\n   * Root dir of capsulse cache (used mostly to copy lock file if used with cache lock file only option)\n   */",
-                      "comment": "Root dir of capsulse cache (used mostly to copy lock file if used with cache lock file only option)"
+                      "comment": "Root dir of capsulse cache (used mostly to copy lock file if used with cache lock file only option)",
+                      "tags": []
                     },
                     "signature": "(property) cacheCapsulesDir?: string | undefined",
                     "name": "cacheCapsulesDir",
@@ -10467,6 +10517,7 @@
                   "character": 3
                 },
                 "raw": "/**\n   *\n   * @param originalCapsule the capsule that contains the original component\n   * @param newBaseDir relative path. (it will be saved inside `this.getRootDirOfAllCapsules()`. the final path of the capsule will be getRootDirOfAllCapsules() + newBaseDir + filenameify(component.id))\n   * @returns a new capsule with the same content of the original capsule but with a new baseDir and all packages\n   * installed in the newBaseDir.\n   */",
+                "comment": "",
                 "tags": [
                   {
                     "__schema": "PropertyLikeTagSchema",
@@ -10684,6 +10735,7 @@
                   "character": 3
                 },
                 "raw": "/** @deprecated use the new function signature with an object parameter instead */",
+                "comment": "",
                 "tags": [
                   {
                     "__schema": "TagSchema",
@@ -11213,7 +11265,8 @@
                     "character": 3
                   },
                   "raw": "/**\n   * include components that exists in nested hosts. for example include components that exist in scope but not in the workspace\n   */",
-                  "comment": "include components that exists in nested hosts. for example include components that exist in scope but not in the workspace"
+                  "comment": "include components that exists in nested hosts. for example include components that exist in scope but not in the workspace",
+                  "tags": []
                 },
                 "signature": "(property) includeFromNestedHosts?: boolean | undefined",
                 "name": "includeFromNestedHosts",
@@ -11243,7 +11296,8 @@
                     "character": 3
                   },
                   "raw": "/**\n   * Force specific host to get the component from.\n   */",
-                  "comment": "Force specific host to get the component from."
+                  "comment": "Force specific host to get the component from.",
+                  "tags": []
                 },
                 "signature": "(property) host?: ComponentFactory | undefined",
                 "name": "host",
@@ -12133,7 +12187,8 @@
                   "character": 3
                 },
                 "raw": "/**\n   * determines whether or not a capsule can theoretically use the dists saved in the last snap, rather than re-compile them.\n   * practically, this optimization is used for components that have typescript as their compiler.\n   */",
-                "comment": "determines whether or not a capsule can theoretically use the dists saved in the last snap, rather than re-compile them.\npractically, this optimization is used for components that have typescript as their compiler."
+                "comment": "determines whether or not a capsule can theoretically use the dists saved in the last snap, rather than re-compile them.\npractically, this optimization is used for components that have typescript as their compiler.",
+                "tags": []
               },
               "signature": "(method) CapsuleList.capsuleUsePreviouslySavedDists(component: Component): Promise<boolean>",
               "name": "capsuleUsePreviouslySavedDists",
@@ -12221,7 +12276,7 @@
                   "_legacy": {
                     "scope": "teambit.component",
                     "name": "isolator",
-                    "version": "1.0.310"
+                    "version": "1.0.311"
                   },
                   "_scope": "teambit.component"
                 }
@@ -12237,7 +12292,7 @@
   "componentId": {
     "scope": "teambit.component",
     "name": "isolator",
-    "version": "1.0.310"
+    "version": "1.0.311"
   },
   "taggedModuleExports": []
 }

package/dist/capsule/container-exec.d.ts

@@ -1,4 +1,3 @@
-/// <reference types="node" />
 import { DuplexBufferStream, Exec, ExecStatus } from '@teambit/capsule';
 import { EventEmitter } from 'events';
 export default class ContainerExec extends EventEmitter implements Exec {

package/dist/capsule/container.d.ts

@@ -1,4 +1,3 @@
-/// <reference types="node" />
 import { AnyFS, NodeFS } from '@teambit/any-fs';
 import { Container, ContainerFactoryOptions, ContainerStatus, Exec, ExecOptions } from '@teambit/capsule';
 import execa from 'execa';

package/dist/{preview-1718853656395.js → preview-1719137078208.js}

@@ -1,5 +1,5 @@
-import * as compositions_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.component_isolator@1.0.310/dist/isolator.composition.js';
-import * as overview_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.component_isolator@1.0.310/dist/isolator.docs.md';
+import * as compositions_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.component_isolator@1.0.311/dist/isolator.composition.js';
+import * as overview_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.component_isolator@1.0.311/dist/isolator.docs.md';
 
 export const compositions = [compositions_0];
 export const overview = [overview_0];

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@teambit/isolator",
-  "version": "1.0.310",
+  "version": "1.0.311",
   "homepage": "https://bit.cloud/teambit/component/isolator",
   "main": "dist/index.js",
   "componentId": {
     "scope": "teambit.component",
     "name": "isolator",
-    "version": "1.0.310"
+    "version": "1.0.311"
   },
   "dependencies": {
     "chalk": "2.4.2",
@@ -26,15 +26,15 @@
     "@teambit/component-id": "1.2.0",
     "@teambit/graph.cleargraph": "0.0.11",
     "@teambit/harmony": "0.4.6",
-    "@teambit/component": "1.0.310",
-    "@teambit/dependency-resolver": "1.0.310",
-    "@teambit/aspect-loader": "1.0.310",
-    "@teambit/cli": "0.0.887",
+    "@teambit/component": "1.0.311",
+    "@teambit/dependency-resolver": "1.0.311",
+    "@teambit/aspect-loader": "1.0.311",
+    "@teambit/cli": "0.0.888",
     "@teambit/component-package-version": "0.0.433",
     "@teambit/dependencies.fs.linked-dependencies": "0.0.9",
-    "@teambit/global-config": "0.0.890",
-    "@teambit/graph": "1.0.310",
-    "@teambit/logger": "0.0.980",
+    "@teambit/global-config": "0.0.891",
+    "@teambit/graph": "1.0.311",
+    "@teambit/logger": "0.0.981",
     "@teambit/workspace.modules.node-modules-linker": "0.0.174"
   },
   "devDependencies": {