Skip to content
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

Fix capabilities semver range for Ember 4 #42

Merged
merged 1 commit into from
Nov 18, 2021

Conversation

simonihmig
Copy link
Contributor

I have seen deprecation warning when running Ember 4 with this addon, as the existing semver range was not correctly accounting for the higher major version (my fault in a previous PR).

I have seen deprecation warning when running Ember 4 with this addon, as the existing semver range was not correctly accounting for the higher major version (my fault in a previous PR).
@simonihmig
Copy link
Contributor Author

So tests for Ember 4 are failing unrelated to these changes here. The dummy app needs ember-auto-import v2, which can be solved by bumping the addon's dependency to v2 (a breaking change, but worthwhile!) or adding eai v2 and webpack only in the ember-try scenarios. See the discussion in emberjs/ember.js#19761.

I would opt for the first option, but it's your call @josemarluedke! 🙂

@josemarluedke
Copy link
Owner

@simonihmig I would go with option one as well. We could also migrate to a V2 addon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants