You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm upgrading an old project from ember-cli-mirage@0.1.15. When I hit the step to upgrade to 0.4.*, I went for 0.4.15 to see what worked. I then saw that this dependency exists:
It looks like at the time of publication, ember-cli-mirage0.4.15 may have been compatible with Node 8. But now it is not.
I don't see any mention of explicit Node version support in ember-cli-mirage. However, going from 0.4.14 to 0.4.15 means that the supported Node version does change.
I don't know if you want to fix this. Feel free to close if not. But if you do, maybe a 0.4.16 release that locks that dependency down would be in order.
Regardless, can you add a breaking change note to 0.4.15 saying this is the case?
The text was updated successfully, but these errors were encountered:
I'm upgrading an old project from ember-cli-mirage@0.1.15. When I hit the step to upgrade to 0.4.*, I went for 0.4.15 to see what worked. I then saw that this dependency exists:
ember-cli-mirage@0.4.15
->ember-auto-import
->jsdom
->webidl-conversions@6.0.0
Unfortunately, webidl-conversions@6.0.0 uses optional catch binding, which means it requires Node 10+. It seems that adding ember-auto-import is the source of this issue.
It looks like at the time of publication, ember-cli-mirage0.4.15 may have been compatible with Node 8. But now it is not.
I don't see any mention of explicit Node version support in ember-cli-mirage. However, going from 0.4.14 to 0.4.15 means that the supported Node version does change.
I don't know if you want to fix this. Feel free to close if not. But if you do, maybe a 0.4.16 release that locks that dependency down would be in order.
Regardless, can you add a breaking change note to 0.4.15 saying this is the case?
The text was updated successfully, but these errors were encountered: