subham25997

Can someone help? I tried following things to fix it: - Deleting node modules and reinstalling deps - Reinstalling bit using **npm i @teambit/bvm** and **bvm install** But it didn't...

@Jinjiang **bit list** shows: ``` ┌───────────────────────────────────────┬─────────────────┬───────────────────┐ │ component ID │ latest in scope │ used in workspace │ ├───────────────────────────────────────┼─────────────────┼───────────────────┤ │ suite360/composables/use-table-header │ 0.0.5 │ 0.0.1 │ ├───────────────────────────────────────┼─────────────────┼───────────────────┤ │ suite360/core/app-navigation │...

@Jinjiang Please find the attached zip folder [suite360-workspace.zip](https://github.com/user-attachments/files/16744428/suite360-workspace.zip)

[suite360-workspace.zip](https://github.com/user-attachments/files/16799249/suite360-workspace.zip) Please follow the following steps to reproduce it. Please try with the attached zip folder, not the previous one. - Tag and export the component to remote scope by...

@Jinjiang ```bash **bit update** gives Root policies ○ @bitdev/general.envs.bit-env (runtime) ^1.0.8 ❯ ^1.0.13 ○ @bitdev/vue.dev-services.linter.vue-eslint-config (runtime) ^0.0.10 ❯ ^0.0.11 ○ @bitdev/vue.dev-services.preview.vue-docs-template (runtime) ^0.0.10 ❯ ^0.0.11 ○ @bitdev/vue.dev-services.preview.vue-mounter (runtime) ^0.0.8 ❯...

In the beginning, I didn't get this issue. Okay let me try with this and will let you know.

I updated and built it, but still getting this issue: 

@Jinjiang Is it something related to capsules path? I changed the capsules path a few days ago, using command: **bit config set capsules_root_base_dir "my-new-path"** and also I am getting these...

@Jinjiang Can you change the default capsule path in your system and try to reproduce this issue?

@joeldenning But **vuetify/components** is not loaded with CDN. It's exported by vuetify itself. Can you please suggest me a proper way to share Vuetify as shared dependency?