-
Notifications
You must be signed in to change notification settings - Fork 377
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
New release for updated dependencies #1202
Comments
If you use yarn, you can try to remove the record ( |
I second that, in my case it did the work too.
In yarn.lock I've removed:
then and it was swapped to:
Now everything's up and running ;) |
Sorry if I'm off track on this, but...
It seems
ember-concurrency
version^0.8.19
is not compatible with Ember 3.6 due to this issue: machty/ember-concurrency#271 (see here too - machty/ember-concurrency#275)Seems the latest
ember-concurrency
resolves that issue.I see that
ember-power-select
was updated fromember-concurrency
^0.8.19
here, df6564fHowever, I don't think there's been a release of
ember-power-select
since then. The yarn pkg registries still have power select using the old concurrency addon, and so power select latest isn't working for me on my newly updated Ember app.Would a new
ember-power-select
release resolve that? In the meantime I updated my dependency like so"ember-power-select": "cibernox/ember-power-select#df6564fbf785bcd29fe9770661176d0ef1ddef8d"
as a workaround inpackage.json
and that's working for the interim.The text was updated successfully, but these errors were encountered: