Closed allthesignals closed 5 years ago
So you're using these Yarn "resolutions" in place of
ember-cli-version-checker
? I saw that you removed this as well. Wasember-cli-version-checker
not catching everything?
@trbmcginnis
So that yarn.lock file gets programmatically generated by yarn
, so I don't actually consciously change anything in the file. It's the side effect of installing new packages.
Somewhere upstream dependencies, something changed and they removed or bumped that dependency.
This entire problem could have something to do with that package, but I'm not completely sure.
This addresses #543 by bumping versions for ember-concurrency, and fixing downstream version conflict issues.
The fix uses the "resolutions" feature in
yarn
to forceyarn
to fetch exact versions of dependencies, ignoring minor version drift.This also prefixes
JOBS=2
inyarn
test to get around the issue documented here: https://github.com/emberjs/ember.js/issues/15641