@teambit/workspace 1.0.1022 → 1.0.1023

package/component-loading-redesign.md

@@ -1,7 +1,7 @@
 # Component Loading Redesign
 
-**Status:** Proposal — under review
-**Last updated:** 2026-06-10 (code references are against `master` @ `59855b104`; line numbers will drift)
+**Status:** Phase 1 shipped; Phase 2 in progress
+**Last updated:** 2026-06-15 (code references are against `master` @ `59855b104`; line numbers will drift)
 
 This document is the source of truth for a multi-phase effort to simplify Bit's component-loading
 mechanism: fewer caches, a staged (lazy) loading pipeline, a single env/aspect load planner, and a
@@ -203,7 +203,7 @@ earlier ones teach us).
 
 ### Phase 2 — Quick perf wins on existing seams
 
-- [ ] Benchmark harness committed + baseline recorded (see §4) — **gate for the rest of the phase**
+- [x] Benchmark harness committed + baseline recorded (see §4) — **gate for the rest of the phase**
 - [ ] Lazy file contents in `ModelComponent.toConsumerComponent`
 - [ ] `bit deps usage`: ids + stored deps instead of full load
 - [ ] IDE metadata endpoint (`api-for-ide.ts`): S0-S2-level data only
@@ -239,17 +239,69 @@ earlier ones teach us).
 
 ## 4. Benchmarks
 
-Method: run on this repository's own workspace (large, real). Record wall-time (median of 3 warm
-runs) and peak RSS. Update this table at every phase boundary; any phase that regresses a number
-must explain why before merging.
-
-| Milestone              | `bit status` | `bit list` | `bit show <comp>` | `bit graph` | Peak RSS |
-| ---------------------- | ------------ | ---------- | ----------------- | ----------- | -------- |
-| Baseline (pre-Phase 2) | —            | —          | —                 | —           | —        |
-| After Phase 2          | —            | —          | —                 | —           | —        |
-| After Phase 3          | —            | —          | —                 | —           | —        |
-| After Phase 4          | —            | —          | —                 | —           | —        |
-| After Phase 5          | —            | —          | —                 | —           | —        |
+Method: `node scripts/bench-component-loading.js --bin=<bit>` runs the four commands below on this
+repository's own workspace (large, real — ~313 components), reporting wall-time (median of 3 warm
+runs, after a discarded warmup) and peak RSS (via `/usr/bin/time`). Run `bit import` first so the
+workspace isn't in a degraded "outdated objects" state. Absolute numbers are **machine-specific** —
+compare deltas on the same machine. Update this table at every phase boundary; any phase that
+regresses a number must explain why before merging.
+
+The `Peak RSS` column is the worst case across the four commands (`bit graph`). Wall-times are
+median seconds. Per-command peak RSS for the baseline: status 1237MB, list 425MB, show 253MB,
+graph 2013MB.
+
+| Milestone              | `bit status` | `bit list` | `bit show <comp>` | `bit graph --json` | Peak RSS |
+| ---------------------- | ------------ | ---------- | ----------------- | ------------------ | -------- |
+| Baseline (pre-Phase 2) | 11.24s       | 1.59s      | 1.73s             | 20.49s             | 2013MB   |
+| After Phase 2          | —            | —          | —                 | —                  | —        |
+| After Phase 3          | —            | —          | —                 | —                  | —        |
+| After Phase 4          | —            | —          | —                 | —                  | —        |
+| After Phase 5          | —            | —          | —                 | —                  | —        |
+
+Baseline measured 2026-06-15 on darwin (Apple silicon), `bit` @ 1.13.222, node v22.20.0,
+`bit show teambit.workspace/workspace`. The two clear hotspots are `bit status` (11s) and
+`bit graph` (20s, 2GB).
+
+### 4.1 Profiling findings (where the warm load time actually goes)
+
+Beyond wall-time, an opt-in aggregate profiler (`BIT_LOAD_PROFILE=1 bit <cmd>`, in
+`@teambit/harmony.modules.load-trace`) sums each load stage's self-time across the whole command.
+Numbers below are aggregate self-time across ~313 components at ~6× concurrency (so wall ≈ total/6).
+
+**`bit status` (warm, ~13s wall):**
+
+| stage                                                       | aggregate self-time | ~wall | note                                          |
+| ----------------------------------------------------------- | ------------------- | ----- | --------------------------------------------- |
+| `legacy-load-deps`                                          | 43s                 | ~7s   | dependency-object materialization (see below) |
+| `on-load` (slot handlers: docs, compositions, schema, pkg…) | 10s                 | ~1.7s | trimmable for non-UI flows                    |
+| `dependency-resolution` (Harmony resolver)                  | 7.7s                | ~1.3s |                                               |
+| `execute-load-slot` (own)                                   | 5.8s                | ~1s   |                                               |
+| `consumer-fs-load` (file content reads)                     | negligible          | —     | not a `status` cost                           |
+
+**`bit graph --json` (warm, ~20s wall; ~7.5s of it is loading):**
+
+| stage                                   | aggregate self-time | note                           |
+| --------------------------------------- | ------------------- | ------------------------------ |
+| `consumer-fs-load` (file content reads) | 5.8s                | dominant load cost for graph   |
+| `legacy-load-deps`                      | 1.2s                | graph uses a lighter load path |
+
+**Key conclusions (validated, not hypothesized):**
+
+- **The dependency FS cache works.** On a warm `bit status`, dep loading is **635 cache hits, 0
+  misses/recomputes**. `legacy-load-deps` is _not_ re-resolving dependencies.
+- **`status`'s dominant cost (~7s wall) is dependency-object _materialization on cache hit_** —
+  `DependenciesData.deserialize` + reconstructing full `Dependency`/`DependencyList` objects +
+  `applyOverrides`, for every component, even though `status` reads little of it. This is the
+  "all-or-nothing, always fully materialize" problem of §1.1 — **structural, not a cache bug.**
+  Reducing it needs the staged/lazy-loading work (defer dependency-object construction), **not a
+  Phase-2 quick fix.** Earlier framing of this as "39s" was aggregate-concurrent self-time, not
+  wall; wall is ~13s.
+- **`graph`'s dominant load cost is file-content reads (`consumer-fs-load`, 5.8s)** → this is what
+  **lazy file contents** (§2.1) targets; validated as a real win for `graph`/scope-side loads, but
+  it does **not** help `status` (whose file reads are negligible).
+- Implication for Phase-2 ordering: lazy file contents helps `graph`; per-command partial loads help
+  `deps usage`/IDE/`remove`/forking; `loadDocs/loadCompositions: false` trims `status`'s slot work
+  (~1.7s). The big `status` number is deferred to the staged-loading phase.
 
 ---
 
@@ -258,7 +310,7 @@ must explain why before merging.
 | Phase                   | State       | OpenSpec change                | PRs                                                 |
 | ----------------------- | ----------- | ------------------------------ | --------------------------------------------------- |
 | 1 — Observability       | done        | `component-load-observability` | [#10418](https://github.com/teambit/bit/pull/10418) |
-| 2 — Quick perf wins     | not started | —                              | —                                                   |
+| 2 — Quick perf wins     | in progress | —                              | —                                                   |
 | 3 — Cache consolidation | not started | —                              | —                                                   |
 | 4 — Staged pipeline     | not started | —                              | —                                                   |
 | 5 — Env planner         | not started | —                              | —                                                   |
@@ -277,3 +329,14 @@ must explain why before merging.
   Span-to-stage mapping for Phase 2 benchmarks: S0=`id-resolution`, S1=`scope-load`/
   `state-from-version`, S2=`extension-merge`+`env-calc`, S3=`consumer-fs-load`,
   S4=`dependency-resolution`+`execute-load-slot`/`on-load:*`.
+- 2026-06-15 — Phase 2 started. Benchmark harness committed (`scripts/bench-component-loading.js`)
+  and baseline recorded in §4 (after `bit import`): `bit status` 11.24s, `bit list` 1.59s,
+  `bit show` 1.73s, `bit graph --json` 20.49s; peak RSS 2.0GB on graph.
+- 2026-06-16 — Profiling done (see §4.1). Added an opt-in aggregate per-stage profiler
+  (`BIT_LOAD_PROFILE=1`) to `@teambit/harmony.modules.load-trace`. Findings: the dependency FS cache
+  works (warm `bit status` = 635 dep-cache hits, 0 misses). `status`'s dominant warm cost (~7s wall)
+  is dependency-_object materialization_ on cache hit (deserialize + reconstruct), not resolution —
+  structural, deferred to staged loading, not a Phase-2 quick win. `graph`'s dominant load cost is
+  file-content reads (`consumer-fs-load`, 5.8s) → the target for lazy file contents. (Correction: an
+  earlier "39s" figure was aggregate-concurrent self-time, not wall; warm wall is ~13s.) Direction
+  for the next Phase-2 PR intentionally left open.

package/dist/component-loading-redesign.md

@@ -1,7 +1,7 @@
 # Component Loading Redesign
 
-**Status:** Proposal — under review
-**Last updated:** 2026-06-10 (code references are against `master` @ `59855b104`; line numbers will drift)
+**Status:** Phase 1 shipped; Phase 2 in progress
+**Last updated:** 2026-06-15 (code references are against `master` @ `59855b104`; line numbers will drift)
 
 This document is the source of truth for a multi-phase effort to simplify Bit's component-loading
 mechanism: fewer caches, a staged (lazy) loading pipeline, a single env/aspect load planner, and a
@@ -203,7 +203,7 @@ earlier ones teach us).
 
 ### Phase 2 — Quick perf wins on existing seams
 
-- [ ] Benchmark harness committed + baseline recorded (see §4) — **gate for the rest of the phase**
+- [x] Benchmark harness committed + baseline recorded (see §4) — **gate for the rest of the phase**
 - [ ] Lazy file contents in `ModelComponent.toConsumerComponent`
 - [ ] `bit deps usage`: ids + stored deps instead of full load
 - [ ] IDE metadata endpoint (`api-for-ide.ts`): S0-S2-level data only
@@ -239,17 +239,69 @@ earlier ones teach us).
 
 ## 4. Benchmarks
 
-Method: run on this repository's own workspace (large, real). Record wall-time (median of 3 warm
-runs) and peak RSS. Update this table at every phase boundary; any phase that regresses a number
-must explain why before merging.
-
-| Milestone              | `bit status` | `bit list` | `bit show <comp>` | `bit graph` | Peak RSS |
-| ---------------------- | ------------ | ---------- | ----------------- | ----------- | -------- |
-| Baseline (pre-Phase 2) | —            | —          | —                 | —           | —        |
-| After Phase 2          | —            | —          | —                 | —           | —        |
-| After Phase 3          | —            | —          | —                 | —           | —        |
-| After Phase 4          | —            | —          | —                 | —           | —        |
-| After Phase 5          | —            | —          | —                 | —           | —        |
+Method: `node scripts/bench-component-loading.js --bin=<bit>` runs the four commands below on this
+repository's own workspace (large, real — ~313 components), reporting wall-time (median of 3 warm
+runs, after a discarded warmup) and peak RSS (via `/usr/bin/time`). Run `bit import` first so the
+workspace isn't in a degraded "outdated objects" state. Absolute numbers are **machine-specific** —
+compare deltas on the same machine. Update this table at every phase boundary; any phase that
+regresses a number must explain why before merging.
+
+The `Peak RSS` column is the worst case across the four commands (`bit graph`). Wall-times are
+median seconds. Per-command peak RSS for the baseline: status 1237MB, list 425MB, show 253MB,
+graph 2013MB.
+
+| Milestone              | `bit status` | `bit list` | `bit show <comp>` | `bit graph --json` | Peak RSS |
+| ---------------------- | ------------ | ---------- | ----------------- | ------------------ | -------- |
+| Baseline (pre-Phase 2) | 11.24s       | 1.59s      | 1.73s             | 20.49s             | 2013MB   |
+| After Phase 2          | —            | —          | —                 | —                  | —        |
+| After Phase 3          | —            | —          | —                 | —                  | —        |
+| After Phase 4          | —            | —          | —                 | —                  | —        |
+| After Phase 5          | —            | —          | —                 | —                  | —        |
+
+Baseline measured 2026-06-15 on darwin (Apple silicon), `bit` @ 1.13.222, node v22.20.0,
+`bit show teambit.workspace/workspace`. The two clear hotspots are `bit status` (11s) and
+`bit graph` (20s, 2GB).
+
+### 4.1 Profiling findings (where the warm load time actually goes)
+
+Beyond wall-time, an opt-in aggregate profiler (`BIT_LOAD_PROFILE=1 bit <cmd>`, in
+`@teambit/harmony.modules.load-trace`) sums each load stage's self-time across the whole command.
+Numbers below are aggregate self-time across ~313 components at ~6× concurrency (so wall ≈ total/6).
+
+**`bit status` (warm, ~13s wall):**
+
+| stage                                                       | aggregate self-time | ~wall | note                                          |
+| ----------------------------------------------------------- | ------------------- | ----- | --------------------------------------------- |
+| `legacy-load-deps`                                          | 43s                 | ~7s   | dependency-object materialization (see below) |
+| `on-load` (slot handlers: docs, compositions, schema, pkg…) | 10s                 | ~1.7s | trimmable for non-UI flows                    |
+| `dependency-resolution` (Harmony resolver)                  | 7.7s                | ~1.3s |                                               |
+| `execute-load-slot` (own)                                   | 5.8s                | ~1s   |                                               |
+| `consumer-fs-load` (file content reads)                     | negligible          | —     | not a `status` cost                           |
+
+**`bit graph --json` (warm, ~20s wall; ~7.5s of it is loading):**
+
+| stage                                   | aggregate self-time | note                           |
+| --------------------------------------- | ------------------- | ------------------------------ |
+| `consumer-fs-load` (file content reads) | 5.8s                | dominant load cost for graph   |
+| `legacy-load-deps`                      | 1.2s                | graph uses a lighter load path |
+
+**Key conclusions (validated, not hypothesized):**
+
+- **The dependency FS cache works.** On a warm `bit status`, dep loading is **635 cache hits, 0
+  misses/recomputes**. `legacy-load-deps` is _not_ re-resolving dependencies.
+- **`status`'s dominant cost (~7s wall) is dependency-object _materialization on cache hit_** —
+  `DependenciesData.deserialize` + reconstructing full `Dependency`/`DependencyList` objects +
+  `applyOverrides`, for every component, even though `status` reads little of it. This is the
+  "all-or-nothing, always fully materialize" problem of §1.1 — **structural, not a cache bug.**
+  Reducing it needs the staged/lazy-loading work (defer dependency-object construction), **not a
+  Phase-2 quick fix.** Earlier framing of this as "39s" was aggregate-concurrent self-time, not
+  wall; wall is ~13s.
+- **`graph`'s dominant load cost is file-content reads (`consumer-fs-load`, 5.8s)** → this is what
+  **lazy file contents** (§2.1) targets; validated as a real win for `graph`/scope-side loads, but
+  it does **not** help `status` (whose file reads are negligible).
+- Implication for Phase-2 ordering: lazy file contents helps `graph`; per-command partial loads help
+  `deps usage`/IDE/`remove`/forking; `loadDocs/loadCompositions: false` trims `status`'s slot work
+  (~1.7s). The big `status` number is deferred to the staged-loading phase.
 
 ---
 
@@ -258,7 +310,7 @@ must explain why before merging.
 | Phase                   | State       | OpenSpec change                | PRs                                                 |
 | ----------------------- | ----------- | ------------------------------ | --------------------------------------------------- |
 | 1 — Observability       | done        | `component-load-observability` | [#10418](https://github.com/teambit/bit/pull/10418) |
-| 2 — Quick perf wins     | not started | —                              | —                                                   |
+| 2 — Quick perf wins     | in progress | —                              | —                                                   |
 | 3 — Cache consolidation | not started | —                              | —                                                   |
 | 4 — Staged pipeline     | not started | —                              | —                                                   |
 | 5 — Env planner         | not started | —                              | —                                                   |
@@ -277,3 +329,14 @@ must explain why before merging.
   Span-to-stage mapping for Phase 2 benchmarks: S0=`id-resolution`, S1=`scope-load`/
   `state-from-version`, S2=`extension-merge`+`env-calc`, S3=`consumer-fs-load`,
   S4=`dependency-resolution`+`execute-load-slot`/`on-load:*`.
+- 2026-06-15 — Phase 2 started. Benchmark harness committed (`scripts/bench-component-loading.js`)
+  and baseline recorded in §4 (after `bit import`): `bit status` 11.24s, `bit list` 1.59s,
+  `bit show` 1.73s, `bit graph --json` 20.49s; peak RSS 2.0GB on graph.
+- 2026-06-16 — Profiling done (see §4.1). Added an opt-in aggregate per-stage profiler
+  (`BIT_LOAD_PROFILE=1`) to `@teambit/harmony.modules.load-trace`. Findings: the dependency FS cache
+  works (warm `bit status` = 635 dep-cache hits, 0 misses). `status`'s dominant warm cost (~7s wall)
+  is dependency-_object materialization_ on cache hit (deserialize + reconstruct), not resolution —
+  structural, deferred to staged loading, not a Phase-2 quick win. `graph`'s dominant load cost is
+  file-content reads (`consumer-fs-load`, 5.8s) → the target for lazy file contents. (Correction: an
+  earlier "39s" figure was aggregate-concurrent self-time, not wall; warm wall is ~13s.) Direction
+  for the next Phase-2 PR intentionally left open.

package/dist/{preview-1781878879101.js → preview-1781891456942.js}

@@ -1,5 +1,5 @@
-import * as compositions_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.workspace_workspace@1.0.1022/dist/workspace.composition.js';
-import * as overview_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.workspace_workspace@1.0.1022/dist/workspace.docs.mdx';
+import * as compositions_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.workspace_workspace@1.0.1023/dist/workspace.composition.js';
+import * as overview_0 from '/home/circleci/Library/Caches/Bit/capsules/8891be5ad/teambit.workspace_workspace@1.0.1023/dist/workspace.docs.mdx';
 
 export const compositions = [compositions_0];
 export const overview = [overview_0];

package/dist/ui/workspace/use-workspace.d.ts

@@ -11,6 +11,7 @@ export declare function useWorkspace(options?: UseWorkspaceOptions): {
     errors?: ReadonlyArray<import("graphql").GraphQLFormattedError> | undefined;
     client: import("@apollo/client").ApolloClient<any>;
     loading: boolean;
+    variables: import("@apollo/client").OperationVariables | undefined;
     observable: import("@apollo/client").ObservableQuery<any, import("@apollo/client").OperationVariables>;
     networkStatus: import("@apollo/client").NetworkStatus;
     called: boolean;
@@ -18,7 +19,6 @@ export declare function useWorkspace(options?: UseWorkspaceOptions): {
     stopPolling: () => void;
     updateQuery: (mapFn: import("@apollo/client").UpdateQueryMapFn<any, import("@apollo/client").OperationVariables>) => void;
     reobserve: (newOptions?: Partial<import("@apollo/client").WatchQueryOptions<import("@apollo/client").OperationVariables, any>> | undefined, newNetworkStatus?: import("@apollo/client").NetworkStatus) => Promise<import("@apollo/client").ApolloQueryResult<any>>;
-    variables: import("@apollo/client").OperationVariables | undefined;
     previousData?: any;
     fetchMore: (options: import("@apollo/client").FetchMoreQueryOptions<import("@apollo/client").OperationVariables, any>) => Promise<import("@apollo/client").ApolloQueryResult<any>>;
     refetch: (variables?: Partial<import("@apollo/client").OperationVariables> | undefined) => Promise<import("@apollo/client").ApolloQueryResult<any>>;

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@teambit/workspace",
-  "version": "1.0.1022",
+  "version": "1.0.1023",
   "homepage": "https://bit.cloud/teambit/workspace/workspace",
   "main": "dist/index.js",
   "componentId": {
     "scope": "teambit.workspace",
     "name": "workspace",
-    "version": "1.0.1022"
+    "version": "1.0.1023"
   },
   "dependencies": {
     "lodash": "4.17.21",
@@ -36,27 +36,40 @@
     "@teambit/toolbox.fs.last-modified": "0.0.15",
     "@teambit/toolbox.path.path": "0.0.17",
     "@teambit/graph.cleargraph": "0.0.11",
+    "@teambit/legacy.constants": "0.0.31",
     "@teambit/component.ui.component-status-resolver": "0.0.510",
-    "@teambit/harmony.modules.load-trace": "0.0.1",
+    "@teambit/harmony.modules.resolved-component": "0.0.515",
+    "@teambit/legacy.utils": "0.0.39",
+    "@teambit/harmony.modules.requireable-component": "0.0.515",
     "@teambit/toolbox.modules.module-resolver": "0.0.20",
+    "@teambit/component-issues": "0.0.174",
     "@teambit/dependencies.modules.packages-excluder": "1.0.8",
+    "@teambit/git.modules.git-executable": "0.0.32",
+    "@teambit/harmony.modules.in-memory-cache": "0.0.35",
     "@teambit/legacy-bit-id": "1.1.3",
     "@teambit/toolbox.path.is-path-inside": "0.0.509",
+    "@teambit/workspace.modules.match-pattern": "0.0.522",
+    "@teambit/component.ui.component-drawer": "0.0.484",
     "@teambit/design.ui.tree": "0.0.16",
+    "@teambit/lanes.hooks.use-lane-components": "0.0.304",
     "@teambit/lanes.hooks.use-lanes": "0.0.293",
     "@teambit/lanes.ui.models.lanes-model": "0.0.233",
+    "@teambit/ui-foundation.ui.side-bar": "0.0.935",
     "@teambit/component.ui.component-filters.component-filter-context": "0.0.242",
     "@teambit/component.ui.component-filters.deprecate-filter": "0.0.244",
+    "@teambit/component.ui.component-filters.env-filter": "0.0.276",
     "@teambit/component.ui.component-filters.show-main-filter": "0.0.237",
     "@teambit/design.ui.surfaces.menu.link-item": "1.0.13",
     "@teambit/ui-foundation.ui.main-dropdown": "0.0.505",
     "@teambit/ui-foundation.ui.menu": "0.0.503",
     "@teambit/ui-foundation.ui.react-router.slot-router": "0.0.523",
     "@teambit/ui-foundation.ui.tree.drawer": "1.0.0",
+    "@teambit/harmony.modules.concurrency": "0.0.32",
     "@teambit/toolbox.promise.map-pool": "0.0.15",
     "@teambit/base-react.themes.theme-switcher": "1.1.2",
     "@teambit/ui-foundation.ui.hooks.use-data-query": "0.0.506",
     "@teambit/workspace.ui.use-workspace-mode": "0.0.3",
+    "@teambit/component-descriptor": "0.0.453",
     "@teambit/ui-foundation.ui.constants.z-indexes": "0.0.504",
     "@teambit/base-ui.surfaces.split-pane.hover-splitter": "1.0.1",
     "@teambit/base-ui.surfaces.split-pane.split-pane": "1.0.0",
@@ -68,63 +81,50 @@
     "@teambit/workspace.hooks.use-url-change-broadcaster": "0.0.2",
     "@teambit/workspace.ui.preserve-workspace-mode": "0.0.3",
     "@teambit/design.ui.tooltip": "0.0.383",
+    "@teambit/preview.ui.preview-placeholder": "0.0.569",
     "@teambit/scopes.scope-id": "0.0.9",
     "@teambit/workspace.ui.load-preview": "0.0.504",
     "@teambit/evangelist.elements.icon": "1.0.5",
     "@teambit/component.filters.base-filter": "0.0.6",
     "@teambit/design.inputs.toggle-button": "0.0.16",
+    "@teambit/cloud.hooks.use-cloud-scopes": "0.0.22",
     "@teambit/explorer.ui.gallery.component-grid": "0.0.496",
     "@teambit/workspace.ui.empty-workspace": "0.0.509",
-    "@teambit/component": "1.0.1022",
-    "@teambit/dependency-resolver": "1.0.1022",
-    "@teambit/envs": "1.0.1022",
-    "@teambit/legacy.extension-data": "0.0.130",
-    "@teambit/legacy.scope": "0.0.128",
-    "@teambit/legacy.consumer-component": "0.0.129",
-    "@teambit/legacy.consumer": "0.0.128",
-    "@teambit/legacy.bit-map": "0.0.185",
-    "@teambit/logger": "0.0.1433",
-    "@teambit/objects": "0.0.529",
-    "@teambit/scope": "1.0.1022",
-    "@teambit/graph": "1.0.1022",
-    "@teambit/cli": "0.0.1340",
-    "@teambit/config-store": "0.0.221",
-    "@teambit/isolator": "1.0.1022",
-    "@teambit/legacy.constants": "0.0.31",
-    "@teambit/component-tree": "1.0.1022",
-    "@teambit/harmony.modules.resolved-component": "0.0.515",
-    "@teambit/legacy.utils": "0.0.39",
-    "@teambit/watcher": "1.0.1022",
-    "@teambit/scope.remotes": "0.0.128",
-    "@teambit/aspect-loader": "1.0.1022",
-    "@teambit/config": "0.0.1515",
-    "@teambit/harmony.modules.requireable-component": "0.0.515",
-    "@teambit/workspace.modules.node-modules-linker": "0.0.359",
-    "@teambit/graphql": "1.0.1022",
-    "@teambit/bundler": "1.0.1022",
-    "@teambit/global-config": "0.0.1344",
-    "@teambit/legacy.consumer-config": "0.0.128",
-    "@teambit/ui": "1.0.1022",
-    "@teambit/variants": "0.0.1608",
-    "@teambit/component-issues": "0.0.174",
-    "@teambit/component.sources": "0.0.180",
-    "@teambit/git.modules.git-executable": "0.0.32",
-    "@teambit/harmony.modules.in-memory-cache": "0.0.35",
-    "@teambit/legacy.component-list": "0.0.182",
-    "@teambit/legacy.scope-api": "0.0.183",
-    "@teambit/workspace.modules.match-pattern": "0.0.522",
-    "@teambit/component.ui.component-drawer": "0.0.484",
-    "@teambit/lanes.hooks.use-lane-components": "0.0.304",
-    "@teambit/ui-foundation.ui.side-bar": "0.0.935",
-    "@teambit/command-bar": "1.0.1022",
-    "@teambit/component.ui.component-filters.env-filter": "0.0.276",
-    "@teambit/sidebar": "1.0.1022",
-    "@teambit/pubsub": "1.0.1022",
-    "@teambit/harmony.modules.concurrency": "0.0.32",
-    "@teambit/component-descriptor": "0.0.453",
-    "@teambit/deprecation": "1.0.1022",
-    "@teambit/preview.ui.preview-placeholder": "0.0.569",
-    "@teambit/cloud.hooks.use-cloud-scopes": "0.0.22"
+    "@teambit/component": "1.0.1023",
+    "@teambit/dependency-resolver": "1.0.1023",
+    "@teambit/envs": "1.0.1023",
+    "@teambit/legacy.extension-data": "0.0.131",
+    "@teambit/legacy.scope": "0.0.129",
+    "@teambit/legacy.consumer-component": "0.0.130",
+    "@teambit/legacy.consumer": "0.0.129",
+    "@teambit/legacy.bit-map": "0.0.186",
+    "@teambit/logger": "0.0.1434",
+    "@teambit/objects": "0.0.530",
+    "@teambit/scope": "1.0.1023",
+    "@teambit/graph": "1.0.1023",
+    "@teambit/cli": "0.0.1341",
+    "@teambit/config-store": "0.0.222",
+    "@teambit/isolator": "1.0.1023",
+    "@teambit/component-tree": "1.0.1023",
+    "@teambit/harmony.modules.load-trace": "0.0.2",
+    "@teambit/watcher": "1.0.1023",
+    "@teambit/scope.remotes": "0.0.129",
+    "@teambit/aspect-loader": "1.0.1023",
+    "@teambit/config": "0.0.1516",
+    "@teambit/workspace.modules.node-modules-linker": "0.0.360",
+    "@teambit/graphql": "1.0.1023",
+    "@teambit/bundler": "1.0.1023",
+    "@teambit/global-config": "0.0.1345",
+    "@teambit/legacy.consumer-config": "0.0.129",
+    "@teambit/ui": "1.0.1023",
+    "@teambit/variants": "0.0.1609",
+    "@teambit/component.sources": "0.0.181",
+    "@teambit/legacy.component-list": "0.0.183",
+    "@teambit/legacy.scope-api": "0.0.184",
+    "@teambit/command-bar": "1.0.1023",
+    "@teambit/sidebar": "1.0.1023",
+    "@teambit/pubsub": "1.0.1023",
+    "@teambit/deprecation": "1.0.1023"
   },
   "devDependencies": {
     "@types/lodash": "4.14.165",