-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Unable to run ember init
after upgrading to 2.6.0
#5973
Comments
@stevenwu what version of ember-cli-htmlbars do you have? Be sure to review https://github.com/ember-cli/ember-cli/blob/master/CONTRIBUTING.md#reporting-a-bug to provide actionable issues. |
i suspect you have a version of ember-cli-htmlbars pre 1.0.7, could you confirm? |
I've been attempting different configurations but have been so far unable to replicate. We will need more information to proceed... |
@stevenwu Can you paste in your package.json? |
I tried to copy package.json and bower.json into a new 2.6.0 project earlier, but couldn't reproduce the erorr. Now I'm trying with a new 2.5.0 project upgrading to 2.6.0. |
@stevenwu My hope was that you could post it here for us to review your dependencies. Is that possible? |
@nathanhammond I've reproduced the error https://github.com/stevenwu/ember-cli-issue-5973 . |
@stevenwu thanks, looking now. |
@nathanhammond / @stevenwu bumping ember-font-awesome to the latest fixed the issue. As it does the right thing. Going to see if we can improve this somehow on our end, although I am unclear on that. |
I can't think of a solution beyond upgrading to the fixed ember-font-awesome. The way I found it was via: which results in:
|
@nathanhammond et. al. we could enable that warning by default? PR to do that: ember-cli/core-object#33 |
@nathanhammond @stefanpenner I also ran into this issue with one of my add-ons. Adding the missing this._super call in the init method did seem to have fixed the issue. However, I didn't see the deprecation warning until (out of curiosity) I temporarily switched Then I was able to see: Not sure if this helps at all. Thanks. |
Had the same problem on my project. Bumping |
@crodriguez1a likely doing that forced NPM to download the latest core-object module, which contained that deprecation? or.. |
Same issue here.
|
Deprecations are enabled by default, if you have issues please follow the deprecations instruction (either updating the addon in question, or fixing the addon in question). This isn't an ember-cli issue, rather we are attempting to transition old add-ons in a helpful way. |
@stefanpenner is there any change to reconsider this until [email protected] or [email protected]? Currently a fresh installation of [email protected] shows three deprecation warnings all of them coming from files in |
@Serabe unfortunately do to how those add-on are wired up, that is the best stack trace we can give. For some add-ons we are able to give a better stack trace and we do, but for lots that information is quite tricky to get. |
the stack trace helps identify how the add-on was instantiated (either in ember-cli, or standalone), but the deprecation also clearly states which dependency needs fixed.
|
@stefanpenner: I see the point on this comment. IMHO, a clean installation of ember-cli should not be raising any kind of deprecation. If ember-cli chooses to include an addon by default, I think this issue tracker would need to address those addons not raising any deprecation. As an example, currently only I would suggest releasing the fix in ember-cli-release as 0.2.9, changing package.json's ember-cli-release version to Thank you! |
@Serabe Your proposed solution isn't unreasonable. It's a time and energy thing. Please see my response on that thread. |
In this case, we enabled the deprecations after 2.6 was already released out of "self defense" (there were a number of issues reported that the deprecation was intended to help with and addon authors had no clue they needed to take action). I think in the future that we should try to land deprecations "on by default" during the beta period, so that addon authors at least have a chance to fix the underlying issues before final/stable releases. I do not think there is much we can do at this point, other than what @Serabe suggested (RE: [email protected] and a [email protected]). |
Unable to run
ember init
when upgrading from2.5.1
to2.6.0
.Output from ember version --verbose (project directory):
Output from ember version --verbose (home directory):
Tried with node
6.1.0
, had same issue.The text was updated successfully, but these errors were encountered: