[BUGFIX release] Make sure newly installed addons are discovered when running ember install
#10014
Conversation
This file contains 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
|
Do you mind targeting the release branch? |
bertdeblock
force-pushed
the
fix-ember-install
branch
from
11b7e1f
to
48e9bd9
Compare
|
@kellyselden Done! |
|
The fix here is needed for #9972, so would appreciate if we could land this soon! 🙏 😀 |
This was referenced Sep 21, 2022
|
When using ember-cli to create a new project, it created the project with Ember 3.22. I then upgraded it using ember-cli-update to 4.7.0 and am experiencing this issue. Am I experiencing this because of this upgrade process or is this still present in 4.7.0? |
Probably because your globally installed version is v3.22?
I don't think this fix has been released yet. |
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Running
ember install addon-namecurrently throws the following error:This regression seems to have been introduced by #9890, even though the fix in that PR seems logical.