@teambit/isolator 1.0.173 → 1.0.174

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (11) hide show
  1. package/artifacts/__bit_junit.xml +1 -1
  2. package/artifacts/preview/teambit_component_isolator-preview.js +1 -1
  3. package/artifacts/schema.json +93 -93
  4. package/dist/isolator.main.runtime.js +4 -2
  5. package/dist/isolator.main.runtime.js.map +1 -1
  6. package/dist/network.d.ts +66 -4
  7. package/dist/network.js +66 -4
  8. package/dist/network.js.map +1 -1
  9. package/dist/preview-1708958940676.js +7 -0
  10. package/package.json +6 -6
  11. package/dist/preview-1708466611462.js +0 -7
package/artifacts/schema.json CHANGED
@@ -38,7 +38,7 @@
38
38
  "__schema": "ClassSchema",
39
39
  "location": {
40
40
  "filePath": "network.ts",
41
- "line": 31,
41
+ "line": 77,
42
42
  "character": 1
43
43
  },
44
44
  "doc": {
@@ -48,8 +48,8 @@
48
48
  "line": 6,
49
49
  "character": 1
50
50
  },
51
- "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 */",
52
- "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)."
51
+ "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 */",
52
+ "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."
53
53
  },
54
54
  "signature": "class Network",
55
55
  "name": "Network",
@@ -58,7 +58,7 @@
58
58
  "__schema": "VariableLikeSchema",
59
59
  "location": {
60
60
  "filePath": "network.ts",
61
- "line": 32,
61
+ "line": 78,
62
62
  "character": 3
63
63
  },
64
64
  "signature": "(property) Network._originalSeeders: ComponentID[] | undefined",
@@ -67,7 +67,7 @@
67
67
  "__schema": "TypeUnionSchema",
68
68
  "location": {
69
69
  "filePath": "network.ts",
70
- "line": 32,
70
+ "line": 78,
71
71
  "character": 21
72
72
  },
73
73
  "types": [
@@ -75,14 +75,14 @@
75
75
  "__schema": "TypeArraySchema",
76
76
  "location": {
77
77
  "filePath": "network.ts",
78
- "line": 32,
78
+ "line": 78,
79
79
  "character": 21
80
80
  },
81
81
  "type": {
82
82
  "__schema": "TypeRefSchema",
83
83
  "location": {
84
84
  "filePath": "network.ts",
85
- "line": 32,
85
+ "line": 78,
86
86
  "character": 21
87
87
  },
88
88
  "name": "ComponentID"
@@ -92,7 +92,7 @@
92
92
  "__schema": "KeywordTypeSchema",
93
93
  "location": {
94
94
  "filePath": "network.ts",
95
- "line": 32,
95
+ "line": 78,
96
96
  "character": 37
97
97
  },
98
98
  "name": "undefined"
@@ -105,7 +105,7 @@
105
105
  "__schema": "ConstructorSchema",
106
106
  "location": {
107
107
  "filePath": "network.ts",
108
- "line": 33,
108
+ "line": 79,
109
109
  "character": 3
110
110
  },
111
111
  "signature": "constructor Network(_graphCapsules: CapsuleList, seedersIds: ComponentID[], _capsulesRootDir: string): Network",
@@ -115,7 +115,7 @@
115
115
  "__schema": "ParameterSchema",
116
116
  "location": {
117
117
  "filePath": "network.ts",
118
- "line": 34,
118
+ "line": 80,
119
119
  "character": 5
120
120
  },
121
121
  "name": "_graphCapsules",
@@ -123,7 +123,7 @@
123
123
  "__schema": "TypeRefSchema",
124
124
  "location": {
125
125
  "filePath": "network.ts",
126
- "line": 34,
126
+ "line": 80,
127
127
  "character": 29
128
128
  },
129
129
  "name": "CapsuleList"
@@ -135,7 +135,7 @@
135
135
  "__schema": "ParameterSchema",
136
136
  "location": {
137
137
  "filePath": "network.ts",
138
- "line": 35,
138
+ "line": 81,
139
139
  "character": 5
140
140
  },
141
141
  "name": "seedersIds",
@@ -143,14 +143,14 @@
143
143
  "__schema": "TypeArraySchema",
144
144
  "location": {
145
145
  "filePath": "network.ts",
146
- "line": 35,
146
+ "line": 81,
147
147
  "character": 25
148
148
  },
149
149
  "type": {
150
150
  "__schema": "TypeRefSchema",
151
151
  "location": {
152
152
  "filePath": "network.ts",
153
- "line": 35,
153
+ "line": 81,
154
154
  "character": 25
155
155
  },
156
156
  "name": "ComponentID"
@@ -163,7 +163,7 @@
163
163
  "__schema": "ParameterSchema",
164
164
  "location": {
165
165
  "filePath": "network.ts",
166
- "line": 36,
166
+ "line": 82,
167
167
  "character": 5
168
168
  },
169
169
  "name": "_capsulesRootDir",
@@ -171,7 +171,7 @@
171
171
  "__schema": "KeywordTypeSchema",
172
172
  "location": {
173
173
  "filePath": "network.ts",
174
- "line": 36,
174
+ "line": 82,
175
175
  "character": 31
176
176
  },
177
177
  "name": "string"
@@ -184,7 +184,7 @@
184
184
  "__schema": "ThisTypeSchema",
185
185
  "location": {
186
186
  "filePath": "network.ts",
187
- "line": 31,
187
+ "line": 77,
188
188
  "character": 1
189
189
  },
190
190
  "name": "Network"
@@ -195,7 +195,7 @@
195
195
  "__schema": "GetAccessorSchema",
196
196
  "location": {
197
197
  "filePath": "network.ts",
198
- "line": 43,
198
+ "line": 102,
199
199
  "character": 3
200
200
  },
201
201
  "signature": "(getter) Network.seedersCapsules: CapsuleList",
@@ -204,7 +204,7 @@
204
204
  "__schema": "TypeRefSchema",
205
205
  "location": {
206
206
  "filePath": "network.ts",
207
- "line": 43,
207
+ "line": 102,
208
208
  "character": 3
209
209
  },
210
210
  "name": "CapsuleList",
@@ -215,7 +215,7 @@
215
215
  "__schema": "GetAccessorSchema",
216
216
  "location": {
217
217
  "filePath": "network.ts",
218
- "line": 56,
218
+ "line": 118,
219
219
  "character": 3
220
220
  },
221
221
  "signature": "(getter) Network.originalSeedersCapsules: CapsuleList",
@@ -224,7 +224,7 @@
224
224
  "__schema": "TypeRefSchema",
225
225
  "location": {
226
226
  "filePath": "network.ts",
227
- "line": 56,
227
+ "line": 118,
228
228
  "character": 3
229
229
  },
230
230
  "name": "CapsuleList",
@@ -235,14 +235,14 @@
235
235
  "__schema": "FunctionLikeSchema",
236
236
  "location": {
237
237
  "filePath": "network.ts",
238
- "line": 69,
238
+ "line": 131,
239
239
  "character": 3
240
240
  },
241
241
  "doc": {
242
242
  "__schema": "DocSchema",
243
243
  "location": {
244
244
  "filePath": "network.ts",
245
- "line": 65,
245
+ "line": 127,
246
246
  "character": 3
247
247
  },
248
248
  "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 */",
@@ -255,7 +255,7 @@
255
255
  "__schema": "InferenceTypeSchema",
256
256
  "location": {
257
257
  "filePath": "network.ts",
258
- "line": 69,
258
+ "line": 131,
259
259
  "character": 3
260
260
  },
261
261
  "type": "Promise<CapsuleList>"
@@ -268,7 +268,7 @@
268
268
  "__schema": "GetAccessorSchema",
269
269
  "location": {
270
270
  "filePath": "network.ts",
271
- "line": 96,
271
+ "line": 158,
272
272
  "character": 3
273
273
  },
274
274
  "signature": "(getter) Network.graphCapsules: CapsuleList",
@@ -277,7 +277,7 @@
277
277
  "__schema": "TypeRefSchema",
278
278
  "location": {
279
279
  "filePath": "network.ts",
280
- "line": 96,
280
+ "line": 158,
281
281
  "character": 3
282
282
  },
283
283
  "name": "CapsuleList",
@@ -288,7 +288,7 @@
288
288
  "__schema": "GetAccessorSchema",
289
289
  "location": {
290
290
  "filePath": "network.ts",
291
- "line": 100,
291
+ "line": 162,
292
292
  "character": 3
293
293
  },
294
294
  "signature": "(getter) Network.capsulesRootDir: string",
@@ -297,7 +297,7 @@
297
297
  "__schema": "TypeRefSchema",
298
298
  "location": {
299
299
  "filePath": "network.ts",
300
- "line": 100,
300
+ "line": 162,
301
301
  "character": 26
302
302
  },
303
303
  "name": "PathOsBasedAbsolute"
@@ -1199,7 +1199,7 @@
1199
1199
  "_legacy": {
1200
1200
  "scope": "teambit.component",
1201
1201
  "name": "isolator",
1202
- "version": "1.0.173"
1202
+ "version": "1.0.174"
1203
1203
  },
1204
1204
  "_scope": "teambit.component"
1205
1205
  }
@@ -2396,7 +2396,7 @@
2396
2396
  "_legacy": {
2397
2397
  "scope": "teambit.component",
2398
2398
  "name": "isolator",
2399
- "version": "1.0.173"
2399
+ "version": "1.0.174"
2400
2400
  },
2401
2401
  "_scope": "teambit.component"
2402
2402
  }
@@ -2672,7 +2672,7 @@
2672
2672
  "_legacy": {
2673
2673
  "scope": "teambit.component",
2674
2674
  "name": "isolator",
2675
- "version": "1.0.173"
2675
+ "version": "1.0.174"
2676
2676
  },
2677
2677
  "_scope": "teambit.component"
2678
2678
  }
@@ -2701,7 +2701,7 @@
2701
2701
  "_legacy": {
2702
2702
  "scope": "teambit.component",
2703
2703
  "name": "isolator",
2704
- "version": "1.0.173"
2704
+ "version": "1.0.174"
2705
2705
  },
2706
2706
  "_scope": "teambit.component"
2707
2707
  }
@@ -3921,7 +3921,7 @@
3921
3921
  "__schema": "FunctionLikeSchema",
3922
3922
  "location": {
3923
3923
  "filePath": "isolator.main.runtime.ts",
3924
- "line": 1114,
3924
+ "line": 1116,
3925
3925
  "character": 3
3926
3926
  },
3927
3927
  "signature": "(method) IsolatorMain.populateComponentsFilesToWriteForCapsule(component: Component, ids: ComponentIdList, legacyScope?: Scope, opts?: IsolateComponentsOptions): Promise<DataToPersist>",
@@ -3931,7 +3931,7 @@
3931
3931
  "__schema": "ParameterSchema",
3932
3932
  "location": {
3933
3933
  "filePath": "isolator.main.runtime.ts",
3934
- "line": 1115,
3934
+ "line": 1117,
3935
3935
  "character": 5
3936
3936
  },
3937
3937
  "name": "component",
@@ -3939,7 +3939,7 @@
3939
3939
  "__schema": "TypeRefSchema",
3940
3940
  "location": {
3941
3941
  "filePath": "isolator.main.runtime.ts",
3942
- "line": 1115,
3942
+ "line": 1117,
3943
3943
  "character": 16
3944
3944
  },
3945
3945
  "name": "Component"
@@ -3951,7 +3951,7 @@
3951
3951
  "__schema": "ParameterSchema",
3952
3952
  "location": {
3953
3953
  "filePath": "isolator.main.runtime.ts",
3954
- "line": 1116,
3954
+ "line": 1118,
3955
3955
  "character": 5
3956
3956
  },
3957
3957
  "name": "ids",
@@ -3959,7 +3959,7 @@
3959
3959
  "__schema": "TypeRefSchema",
3960
3960
  "location": {
3961
3961
  "filePath": "isolator.main.runtime.ts",
3962
- "line": 1116,
3962
+ "line": 1118,
3963
3963
  "character": 10
3964
3964
  },
3965
3965
  "name": "ComponentIdList"
@@ -3971,7 +3971,7 @@
3971
3971
  "__schema": "ParameterSchema",
3972
3972
  "location": {
3973
3973
  "filePath": "isolator.main.runtime.ts",
3974
- "line": 1117,
3974
+ "line": 1119,
3975
3975
  "character": 5
3976
3976
  },
3977
3977
  "name": "legacyScope",
@@ -3979,7 +3979,7 @@
3979
3979
  "__schema": "TypeRefSchema",
3980
3980
  "location": {
3981
3981
  "filePath": "isolator.main.runtime.ts",
3982
- "line": 1117,
3982
+ "line": 1119,
3983
3983
  "character": 19
3984
3984
  },
3985
3985
  "name": "Scope"
@@ -3991,7 +3991,7 @@
3991
3991
  "__schema": "ParameterSchema",
3992
3992
  "location": {
3993
3993
  "filePath": "isolator.main.runtime.ts",
3994
- "line": 1118,
3994
+ "line": 1120,
3995
3995
  "character": 5
3996
3996
  },
3997
3997
  "name": "opts",
@@ -3999,7 +3999,7 @@
3999
3999
  "__schema": "TypeRefSchema",
4000
4000
  "location": {
4001
4001
  "filePath": "isolator.main.runtime.ts",
4002
- "line": 1118,
4002
+ "line": 1120,
4003
4003
  "character": 12
4004
4004
  },
4005
4005
  "name": "IsolateComponentsOptions"
@@ -4012,7 +4012,7 @@
4012
4012
  "__schema": "TypeRefSchema",
4013
4013
  "location": {
4014
4014
  "filePath": "isolator.main.runtime.ts",
4015
- "line": 1119,
4015
+ "line": 1121,
4016
4016
  "character": 6
4017
4017
  },
4018
4018
  "name": "Promise",
@@ -4021,7 +4021,7 @@
4021
4021
  "__schema": "TypeRefSchema",
4022
4022
  "location": {
4023
4023
  "filePath": "isolator.main.runtime.ts",
4024
- "line": 1119,
4024
+ "line": 1121,
4025
4025
  "character": 14
4026
4026
  },
4027
4027
  "name": "DataToPersist"
@@ -5258,7 +5258,7 @@
5258
5258
  "_legacy": {
5259
5259
  "scope": "teambit.component",
5260
5260
  "name": "isolator",
5261
- "version": "1.0.173"
5261
+ "version": "1.0.174"
5262
5262
  },
5263
5263
  "_scope": "teambit.component"
5264
5264
  }
@@ -5283,7 +5283,7 @@
5283
5283
  "__schema": "ClassSchema",
5284
5284
  "location": {
5285
5285
  "filePath": "network.ts",
5286
- "line": 31,
5286
+ "line": 77,
5287
5287
  "character": 1
5288
5288
  },
5289
5289
  "doc": {
@@ -5293,8 +5293,8 @@
5293
5293
  "line": 6,
5294
5294
  "character": 1
5295
5295
  },
5296
- "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 */",
5297
- "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)."
5296
+ "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 */",
5297
+ "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."
5298
5298
  },
5299
5299
  "signature": "class Network",
5300
5300
  "name": "Network",
@@ -5303,7 +5303,7 @@
5303
5303
  "__schema": "VariableLikeSchema",
5304
5304
  "location": {
5305
5305
  "filePath": "network.ts",
5306
- "line": 32,
5306
+ "line": 78,
5307
5307
  "character": 3
5308
5308
  },
5309
5309
  "signature": "(property) Network._originalSeeders: ComponentID[] | undefined",
@@ -5312,7 +5312,7 @@
5312
5312
  "__schema": "TypeUnionSchema",
5313
5313
  "location": {
5314
5314
  "filePath": "network.ts",
5315
- "line": 32,
5315
+ "line": 78,
5316
5316
  "character": 21
5317
5317
  },
5318
5318
  "types": [
@@ -5320,14 +5320,14 @@
5320
5320
  "__schema": "TypeArraySchema",
5321
5321
  "location": {
5322
5322
  "filePath": "network.ts",
5323
- "line": 32,
5323
+ "line": 78,
5324
5324
  "character": 21
5325
5325
  },
5326
5326
  "type": {
5327
5327
  "__schema": "TypeRefSchema",
5328
5328
  "location": {
5329
5329
  "filePath": "network.ts",
5330
- "line": 32,
5330
+ "line": 78,
5331
5331
  "character": 21
5332
5332
  },
5333
5333
  "name": "ComponentID"
@@ -5337,7 +5337,7 @@
5337
5337
  "__schema": "KeywordTypeSchema",
5338
5338
  "location": {
5339
5339
  "filePath": "network.ts",
5340
- "line": 32,
5340
+ "line": 78,
5341
5341
  "character": 37
5342
5342
  },
5343
5343
  "name": "undefined"
@@ -5350,7 +5350,7 @@
5350
5350
  "__schema": "ConstructorSchema",
5351
5351
  "location": {
5352
5352
  "filePath": "network.ts",
5353
- "line": 33,
5353
+ "line": 79,
5354
5354
  "character": 3
5355
5355
  },
5356
5356
  "signature": "constructor Network(_graphCapsules: CapsuleList, seedersIds: ComponentID[], _capsulesRootDir: string): Network",
@@ -5360,7 +5360,7 @@
5360
5360
  "__schema": "ParameterSchema",
5361
5361
  "location": {
5362
5362
  "filePath": "network.ts",
5363
- "line": 34,
5363
+ "line": 80,
5364
5364
  "character": 5
5365
5365
  },
5366
5366
  "name": "_graphCapsules",
@@ -5368,7 +5368,7 @@
5368
5368
  "__schema": "TypeRefSchema",
5369
5369
  "location": {
5370
5370
  "filePath": "network.ts",
5371
- "line": 34,
5371
+ "line": 80,
5372
5372
  "character": 29
5373
5373
  },
5374
5374
  "name": "CapsuleList"
@@ -5380,7 +5380,7 @@
5380
5380
  "__schema": "ParameterSchema",
5381
5381
  "location": {
5382
5382
  "filePath": "network.ts",
5383
- "line": 35,
5383
+ "line": 81,
5384
5384
  "character": 5
5385
5385
  },
5386
5386
  "name": "seedersIds",
@@ -5388,14 +5388,14 @@
5388
5388
  "__schema": "TypeArraySchema",
5389
5389
  "location": {
5390
5390
  "filePath": "network.ts",
5391
- "line": 35,
5391
+ "line": 81,
5392
5392
  "character": 25
5393
5393
  },
5394
5394
  "type": {
5395
5395
  "__schema": "TypeRefSchema",
5396
5396
  "location": {
5397
5397
  "filePath": "network.ts",
5398
- "line": 35,
5398
+ "line": 81,
5399
5399
  "character": 25
5400
5400
  },
5401
5401
  "name": "ComponentID"
@@ -5408,7 +5408,7 @@
5408
5408
  "__schema": "ParameterSchema",
5409
5409
  "location": {
5410
5410
  "filePath": "network.ts",
5411
- "line": 36,
5411
+ "line": 82,
5412
5412
  "character": 5
5413
5413
  },
5414
5414
  "name": "_capsulesRootDir",
@@ -5416,7 +5416,7 @@
5416
5416
  "__schema": "KeywordTypeSchema",
5417
5417
  "location": {
5418
5418
  "filePath": "network.ts",
5419
- "line": 36,
5419
+ "line": 82,
5420
5420
  "character": 31
5421
5421
  },
5422
5422
  "name": "string"
@@ -5429,7 +5429,7 @@
5429
5429
  "__schema": "ThisTypeSchema",
5430
5430
  "location": {
5431
5431
  "filePath": "network.ts",
5432
- "line": 31,
5432
+ "line": 77,
5433
5433
  "character": 1
5434
5434
  },
5435
5435
  "name": "Network"
@@ -5440,7 +5440,7 @@
5440
5440
  "__schema": "GetAccessorSchema",
5441
5441
  "location": {
5442
5442
  "filePath": "network.ts",
5443
- "line": 43,
5443
+ "line": 102,
5444
5444
  "character": 3
5445
5445
  },
5446
5446
  "signature": "(getter) Network.seedersCapsules: CapsuleList",
@@ -5449,7 +5449,7 @@
5449
5449
  "__schema": "TypeRefSchema",
5450
5450
  "location": {
5451
5451
  "filePath": "network.ts",
5452
- "line": 43,
5452
+ "line": 102,
5453
5453
  "character": 3
5454
5454
  },
5455
5455
  "name": "CapsuleList",
@@ -5460,7 +5460,7 @@
5460
5460
  "__schema": "GetAccessorSchema",
5461
5461
  "location": {
5462
5462
  "filePath": "network.ts",
5463
- "line": 56,
5463
+ "line": 118,
5464
5464
  "character": 3
5465
5465
  },
5466
5466
  "signature": "(getter) Network.originalSeedersCapsules: CapsuleList",
@@ -5469,7 +5469,7 @@
5469
5469
  "__schema": "TypeRefSchema",
5470
5470
  "location": {
5471
5471
  "filePath": "network.ts",
5472
- "line": 56,
5472
+ "line": 118,
5473
5473
  "character": 3
5474
5474
  },
5475
5475
  "name": "CapsuleList",
@@ -5480,14 +5480,14 @@
5480
5480
  "__schema": "FunctionLikeSchema",
5481
5481
  "location": {
5482
5482
  "filePath": "network.ts",
5483
- "line": 69,
5483
+ "line": 131,
5484
5484
  "character": 3
5485
5485
  },
5486
5486
  "doc": {
5487
5487
  "__schema": "DocSchema",
5488
5488
  "location": {
5489
5489
  "filePath": "network.ts",
5490
- "line": 65,
5490
+ "line": 127,
5491
5491
  "character": 3
5492
5492
  },
5493
5493
  "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 */",
@@ -5500,7 +5500,7 @@
5500
5500
  "__schema": "InferenceTypeSchema",
5501
5501
  "location": {
5502
5502
  "filePath": "network.ts",
5503
- "line": 69,
5503
+ "line": 131,
5504
5504
  "character": 3
5505
5505
  },
5506
5506
  "type": "Promise<CapsuleList>"
@@ -5513,7 +5513,7 @@
5513
5513
  "__schema": "GetAccessorSchema",
5514
5514
  "location": {
5515
5515
  "filePath": "network.ts",
5516
- "line": 96,
5516
+ "line": 158,
5517
5517
  "character": 3
5518
5518
  },
5519
5519
  "signature": "(getter) Network.graphCapsules: CapsuleList",
@@ -5522,7 +5522,7 @@
5522
5522
  "__schema": "TypeRefSchema",
5523
5523
  "location": {
5524
5524
  "filePath": "network.ts",
5525
- "line": 96,
5525
+ "line": 158,
5526
5526
  "character": 3
5527
5527
  },
5528
5528
  "name": "CapsuleList",
@@ -5533,7 +5533,7 @@
5533
5533
  "__schema": "GetAccessorSchema",
5534
5534
  "location": {
5535
5535
  "filePath": "network.ts",
5536
- "line": 100,
5536
+ "line": 162,
5537
5537
  "character": 3
5538
5538
  },
5539
5539
  "signature": "(getter) Network.capsulesRootDir: string",
@@ -5542,7 +5542,7 @@
5542
5542
  "__schema": "TypeRefSchema",
5543
5543
  "location": {
5544
5544
  "filePath": "network.ts",
5545
- "line": 100,
5545
+ "line": 162,
5546
5546
  "character": 26
5547
5547
  },
5548
5548
  "name": "PathOsBasedAbsolute"
@@ -5600,7 +5600,7 @@
5600
5600
  "line": 14,
5601
5601
  "character": 3
5602
5602
  },
5603
- "signature": "(property) BitExecOption.stdio?: number | Stream | \"pipe\" | \"ignore\" | \"inherit\" | \"ipc\" | undefined",
5603
+ "signature": "(property) BitExecOption.stdio?: number | Stream | \"ignore\" | \"pipe\" | \"inherit\" | \"ipc\" | undefined",
5604
5604
  "name": "stdio",
5605
5605
  "type": {
5606
5606
  "__schema": "TypeUnionSchema",
@@ -5700,7 +5700,7 @@
5700
5700
  "_legacy": {
5701
5701
  "scope": "teambit.component",
5702
5702
  "name": "isolator",
5703
- "version": "1.0.173"
5703
+ "version": "1.0.174"
5704
5704
  },
5705
5705
  "_scope": "teambit.component"
5706
5706
  }
@@ -5761,7 +5761,7 @@
5761
5761
  "_legacy": {
5762
5762
  "scope": "teambit.component",
5763
5763
  "name": "isolator",
5764
- "version": "1.0.173"
5764
+ "version": "1.0.174"
5765
5765
  },
5766
5766
  "_scope": "teambit.component"
5767
5767
  }
@@ -6661,7 +6661,7 @@
6661
6661
  "_legacy": {
6662
6662
  "scope": "teambit.component",
6663
6663
  "name": "isolator",
6664
- "version": "1.0.173"
6664
+ "version": "1.0.174"
6665
6665
  },
6666
6666
  "_scope": "teambit.component"
6667
6667
  }
@@ -7902,7 +7902,7 @@
7902
7902
  "_legacy": {
7903
7903
  "scope": "teambit.component",
7904
7904
  "name": "isolator",
7905
- "version": "1.0.173"
7905
+ "version": "1.0.174"
7906
7906
  },
7907
7907
  "_scope": "teambit.component"
7908
7908
  }
@@ -8189,7 +8189,7 @@
8189
8189
  "_legacy": {
8190
8190
  "scope": "teambit.component",
8191
8191
  "name": "isolator",
8192
- "version": "1.0.173"
8192
+ "version": "1.0.174"
8193
8193
  },
8194
8194
  "_scope": "teambit.component"
8195
8195
  }
@@ -8218,7 +8218,7 @@
8218
8218
  "_legacy": {
8219
8219
  "scope": "teambit.component",
8220
8220
  "name": "isolator",
8221
- "version": "1.0.173"
8221
+ "version": "1.0.174"
8222
8222
  },
8223
8223
  "_scope": "teambit.component"
8224
8224
  }
@@ -10578,7 +10578,7 @@
10578
10578
  "__schema": "FunctionLikeSchema",
10579
10579
  "location": {
10580
10580
  "filePath": "isolator.main.runtime.ts",
10581
- "line": 1114,
10581
+ "line": 1116,
10582
10582
  "character": 3
10583
10583
  },
10584
10584
  "signature": "(method) IsolatorMain.populateComponentsFilesToWriteForCapsule(component: Component, ids: ComponentIdList, legacyScope?: Scope, opts?: IsolateComponentsOptions): Promise<DataToPersist>",
@@ -10588,7 +10588,7 @@
10588
10588
  "__schema": "ParameterSchema",
10589
10589
  "location": {
10590
10590
  "filePath": "isolator.main.runtime.ts",
10591
- "line": 1115,
10591
+ "line": 1117,
10592
10592
  "character": 5
10593
10593
  },
10594
10594
  "name": "component",
@@ -10596,7 +10596,7 @@
10596
10596
  "__schema": "TypeRefSchema",
10597
10597
  "location": {
10598
10598
  "filePath": "isolator.main.runtime.ts",
10599
- "line": 1115,
10599
+ "line": 1117,
10600
10600
  "character": 16
10601
10601
  },
10602
10602
  "name": "Component"
@@ -10608,7 +10608,7 @@
10608
10608
  "__schema": "ParameterSchema",
10609
10609
  "location": {
10610
10610
  "filePath": "isolator.main.runtime.ts",
10611
- "line": 1116,
10611
+ "line": 1118,
10612
10612
  "character": 5
10613
10613
  },
10614
10614
  "name": "ids",
@@ -10616,7 +10616,7 @@
10616
10616
  "__schema": "TypeRefSchema",
10617
10617
  "location": {
10618
10618
  "filePath": "isolator.main.runtime.ts",
10619
- "line": 1116,
10619
+ "line": 1118,
10620
10620
  "character": 10
10621
10621
  },
10622
10622
  "name": "ComponentIdList"
@@ -10628,7 +10628,7 @@
10628
10628
  "__schema": "ParameterSchema",
10629
10629
  "location": {
10630
10630
  "filePath": "isolator.main.runtime.ts",
10631
- "line": 1117,
10631
+ "line": 1119,
10632
10632
  "character": 5
10633
10633
  },
10634
10634
  "name": "legacyScope",
@@ -10636,7 +10636,7 @@
10636
10636
  "__schema": "TypeRefSchema",
10637
10637
  "location": {
10638
10638
  "filePath": "isolator.main.runtime.ts",
10639
- "line": 1117,
10639
+ "line": 1119,
10640
10640
  "character": 19
10641
10641
  },
10642
10642
  "name": "Scope"
@@ -10648,7 +10648,7 @@
10648
10648
  "__schema": "ParameterSchema",
10649
10649
  "location": {
10650
10650
  "filePath": "isolator.main.runtime.ts",
10651
- "line": 1118,
10651
+ "line": 1120,
10652
10652
  "character": 5
10653
10653
  },
10654
10654
  "name": "opts",
@@ -10656,7 +10656,7 @@
10656
10656
  "__schema": "TypeRefSchema",
10657
10657
  "location": {
10658
10658
  "filePath": "isolator.main.runtime.ts",
10659
- "line": 1118,
10659
+ "line": 1120,
10660
10660
  "character": 12
10661
10661
  },
10662
10662
  "name": "IsolateComponentsOptions"
@@ -10669,7 +10669,7 @@
10669
10669
  "__schema": "TypeRefSchema",
10670
10670
  "location": {
10671
10671
  "filePath": "isolator.main.runtime.ts",
10672
- "line": 1119,
10672
+ "line": 1121,
10673
10673
  "character": 6
10674
10674
  },
10675
10675
  "name": "Promise",
@@ -10678,7 +10678,7 @@
10678
10678
  "__schema": "TypeRefSchema",
10679
10679
  "location": {
10680
10680
  "filePath": "isolator.main.runtime.ts",
10681
- "line": 1119,
10681
+ "line": 1121,
10682
10682
  "character": 14
10683
10683
  },
10684
10684
  "name": "DataToPersist"
@@ -11076,7 +11076,7 @@
11076
11076
  "__schema": "UnImplementedSchema",
11077
11077
  "location": {
11078
11078
  "filePath": "isolator.main.runtime.ts",
11079
- "line": 1246,
11079
+ "line": 1248,
11080
11080
  "character": 1
11081
11081
  },
11082
11082
  "name": "IsolatorAspect.addRuntime(IsolatorMain);",
@@ -11648,7 +11648,7 @@
11648
11648
  "_legacy": {
11649
11649
  "scope": "teambit.component",
11650
11650
  "name": "isolator",
11651
- "version": "1.0.173"
11651
+ "version": "1.0.174"
11652
11652
  },
11653
11653
  "_scope": "teambit.component"
11654
11654
  }
@@ -11664,7 +11664,7 @@
11664
11664
  "componentId": {
11665
11665
  "scope": "teambit.component",
11666
11666
  "name": "isolator",
11667
- "version": "1.0.173"
11667
+ "version": "1.0.174"
11668
11668
  },
11669
11669
  "taggedModuleExports": []
11670
11670
  }