Open psteininger opened 6 years ago
I'm also seeing this. @rwjblue any idea what could be causing this?
I think it is a regression in ember-cli where we essentially require the app/
directory to be present. We should confirm, and make sure it is reported upstream...
Sounds good. I was planning to migrate most of my apps, but maybe that isn't a good idea yet? I'm not sure when module unification is supposed to land.
I have the same problem with :
ember-cli: 2.18.0-beta.1
node: 8.9.1
os: darwin x64
Any update ?
This is related to / possible dupe https://github.com/ember-cli/ember-cli/issues/7343. Upon catching that error, I saw the one mentioned in this ticket appear.
Any ideas when this might be fixed? I'm unsure when module unification is supposed to drop, so no real hurry, but would like to start getting used to the new directory structure ahead of time.
I reproduced this issue and it comes down to having an ember-cli version that doesn't have MU enabled.
AFAIK you need to use ember-cli from master if you want to try turning on MU.
You can verify by looking in node_modules/ember-cli/lib/experiments/index.html
. If it says MODULE_UNIFICATION: false
, it's not going to work.
The exact place where the code tries to watch app
is here:
I'm linking to code from the latest stable release, master has already changed from this.
after running
ember-module-migrator
even on a brand new Ember 2.16 project one get's the following