-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Adding ember-data
to project breaks the build complaining about two separate instances of a plugin
#7430
Comments
I have the same issue when trying to upgrade to latest Ember using ember-cli-update |
Same issue on a longstanding app. Seems fine in 3.23, throws like this in 3.24. Seems related to this: #7369 |
@andreisebastianc-ccc I'm guessing your reproduction steps including blowing away What does it show in your project when you run |
@snewcomer Yes, it reproduces regardless of what I do to the
|
As we no longer depend on |
@runspired I also ran into this issue, after running Edit: reverting to |
Also wondering this @runspired, I tried using |
@jcardali you'd want to figure out whatever else was bringing in ordered-set and figure out why it was a different version. |
I'm pretty sure |
@jcardali yes for current release it does, but I think this error is because something else is also installing it and bringing a different version. |
@mehulkar was able to debug a reproduction of this and I was able to help him narrow down to the specific problem being multiple versions of ember-compatibility-helpers being present, some of which do not have a fix for adding duplicate plugins for a scenario that @ember/ordered-set can trigger. That issue was described and fixed in ember-cli/ember-compatibility-helpers#36 which was included in the I've known for some time this had to be a dependency drift related issue since our own tests, test apps, test addons, and external partner apps and addons had not triggered this. In each case encountered blowing away node_modules and the lock file and then re-installing had resolved the issue. Now that the specific offender is known, a simpler fix is to update just the specific dep. For yarn users
or
For npm users
|
Unfortunately that still does not address the issue, it seems I have no choice but to wait for these underlying packages to get to
|
Assuming those packages don’t pin to 1.2.0, you can choose the nuclear option (delete the lock file and node_modules) and run npm install. |
As seen here: emberjs/data#7430 (comment)
I have a client-only app that I'm transitioning to consume data from a server with DB. I proceeded to add Mirage for mocks and Ember Data.
I ran
ember install ember-data
.Tried removing Mirage and installing ember-data and got the same result. Removed lockfile and ran npm install and got the same result.
This may be a thing that's easy to fix if you know what you're looking for but I did not find useful info about how to handle this problem.
Let me know if there's something else I can do to provide more info.
Description
Stack Trace
Original package.json
Versions
Tried with both 3.25 and 3.24 and got the same result, an import and some content inlined.
In ember-cli-build.js I have tailwind and purgecss config.
ember-cli-build.js
The text was updated successfully, but these errors were encountered: