fix: resolve env extends from remote during bit new#9981
Merged
Conversation
When running bit new with templates that have custom envs extending other envs, the extends resolution would fail because the base env wasn't available in the (empty) workspace. This adds a fallback to fetch env manifests from remote components when they can't be found locally, enabling proper extends resolution during workspace generation.
Jinjiang
approved these changes
Sep 4, 2025
GiladShoham
approved these changes
Sep 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the issue where
bit newfails when using templates with custom envs that extend other envs.Problem
When running
bit newwith a template that creates a custom env extending another env (likebitdev.vue/vue-env), the extends resolution fails withVersionNotFoundOnFSerror because:Solution
Added a fallback mechanism in
workspace.tsthat:VersionNotFoundOnFSerrors during env manifest resolutionThis approach is:
bit newTest Plan
Tested with:
Before: Failed with
VersionNotFoundOnFSerrorAfter: Successfully creates workspace and compiles components
The fix resolves the original extends resolution error and allows
bit newto proceed successfully.