Closed gzurbach closed 3 years ago
In case this is useful, I ran npm list ember-compatibility-helpers
in my app to see where it's used:
webapp@0.0.0 /Users/me/repos/webapp
├─┬ @ember/test-helpers@2.2.6
│ └─┬ ember-destroyable-polyfill@2.0.3
│ └── ember-compatibility-helpers@1.2.4
├─┬ @glimmer/component@1.0.3
│ └── ember-compatibility-helpers@1.1.2
├─┬ ember-cli-meta-tags@6.1.2
│ └── ember-compatibility-helpers@1.1.2 deduped
├─┬ ember-data@3.24.2
│ ├─┬ @ember-data/model@3.24.2
│ │ └── ember-compatibility-helpers@1.2.4
│ └─┬ @ember/ordered-set@4.0.0
│ └── ember-compatibility-helpers@1.1.2 deduped
├─┬ ember-flatpickr@3.0.1
│ └─┬ @ember/render-modifiers@1.0.2
│ └─┬ ember-modifier-manager-polyfill@1.2.0
│ └── ember-compatibility-helpers@1.2.2
├─┬ ember-router-scroll@4.0.0
│ ├─┬ ember-app-scheduler@5.1.2
│ │ ├── ember-compatibility-helpers@1.1.2 deduped
│ │ └─┬ ember-destroyable-polyfill@2.0.2
│ │ └── ember-compatibility-helpers@1.2.2
│ └── ember-compatibility-helpers@1.1.2 deduped
└─┬ ember-welcome-page@4.0.0
└── ember-compatibility-helpers@1.1.2 deduped
I can see that @ember/ordered-set@4.0.0
has a dependency on ember-compatibility-helpers@1.1.2
, which seem to be where things are blowing up?
I'm seeing exactly the same error, also when upgrading to 3.24 (from 3.23). Like you, I don't know much about babel to understand what's going on... I'll look into it and will report if I find out anything.
It looks like it's in ember-data
3.24. There's more info about the issue on this thread: https://github.com/emberjs/data/issues/7430
The proposed fix (npm --depth 20 update ember-compatibility-helpers
) worked for me.
@YoranBrondsema Thanks for the tip! I ended up nuking my node_modules
+ package-lock.json
then ran a fresh npm install
which solved the issue 😄
Hi there,
I am in the process of upgrading my app from Ember 3.20 to 3.24. After running
npm install
, I tried to runember serve
but I am getting the following error:I am not familiar enough with Babel at this point to understand what's going on. I am mostly curious to know if others had encountered this issue. I will do some digging as well and report back if I find anything.