downgrade ember-cli dependency to support a wider range of ember-source #2321
+26
−14
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.
Most of the time this won't be a problem for people since ember-cli can usually be upgraded independently of your app, but this breaks for anyone trying to use the codemod with [email protected] because of the bowerDependencies deprecation and removal in ember-cli@5
The issue I have here is that we kinda want a peer, but we don't actually install the codemod 🙈 doesnpx
consider the cwd when thinking about peers? What is the best way forward here? should I be doing an explicit resolve from cwd and dropping the dependency altogether? Thoughts?This PR downgrades the ember-cli dependency to 4.12 which gives us a balance of supporting 3.28 and also being the first version that works with an async function returned from ember-cli-build 😂 we're very lucky this version is so perfect