Jinjiang

@subham25997 may I know the `bit list` and `bit envs` output? Honestly, I've met this issue before (on macOS) but this time w/ a single vue component on vue-env v1.1.3...

@subham25997 sorry I still couldn't reproduce it. Would you mind sending me your workspace with a zip file? the `node_modules` folder could be skipped since I can run `bit install`...

@subham25997 interestingly, I still couldn't reproduce it. And after some modifications this zip works from my side: [issue-9172-suite360-workspace.zip](https://github.com/user-attachments/files/16756278/issue-9172-suite360-workspace.zip) what I've changed (you can also refer to the diff file): 1....

I've tried the new one again. It worked as well. Maybe there are some other factors caused this error.🤔 Would you mind sharing the output of `bit update` (just share...

I see. Would you mind updating only `@bitdev/general.envs.bit-env` from 1.0.8 to 1.0.13 and try to build again? Also, do you meet the same build error if you just start from...

@subham25997 this warning should be fine. but speaking of the capsule path, i'm not sure about that. technically the only chance to affect the build result might be somewhere with...

I actually have tried multiple different workspace paths which have different corresponding capsule hashes. So far I didn't reproduce the issue yet.

Update: Good news, I've reproduced it in another casual component. Hopefully this time it could be fixed. Will keep you posted.

New `bitdev.vue/vue-env` has been released (v1.1.5) which should have fixed this issue. Please have a check. 🙏 For existing custom vue env, you can try to: 1. update its dependency...

We don't have made an example yet but technically yes. It's on our plan list.