-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade ember-cli
to latest throughout test infrastructure
#961
Conversation
294cbfd
to
a68c976
Compare
Failures appear related to engines. |
Oh boy, the failure here is juicy! TL;DR embroider's test-setup has never worked correctly, and regularly mixes multiple ember-cli versions in it's test scenario node_module tree. In this case, we have: project has the following (relevant) dependency links:
This hasn't manifested before, because the relevant code in ember-cli hasn't changed recently, now that it has it has exposed the issue. The fact the engines (and other) dependencies introduce a dependency cycle is problematic in general, given that ember-engines is essentially frozen and that embroider aims to replace it, means a work-around in this project is likely the most appropriate. Given this, I believe the solution is to have fixture ember-engine dependencies which correctly link the given scenarios ember-cli's version |
I think the above commit fixes the peerDeps problem. It's not ready to merge until we get stable releases of fixturify-project and scenario-tester, after stefanpenner/node-fixturify-project#50 is reviewed and released. This is pointing at my own alpha releases just to test it. |
@ef4 I'm assuming you are looking into the failures:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ember-cli
to latest throughout test infrastructure
No description provided.