VeryGoodOpenSource / mockingjay

A package that makes it easy to mock, test, and verify navigation in Flutter. Created by Very Good Ventures πŸ¦„
https://pub.dev/packages/mockingjay
MIT License
112 stars 7 forks source link

Unable to use latest version of build_runner 2.3.2 with mockingjay #41

Closed prolificcoder closed 1 year ago

prolificcoder commented 1 year ago

Describe the bug If a project has build_runner 2.3.2 (latest of writing), mockingjay 0.3.0 won't work

Expected behavior flutter pub get should work

logs The current Dart SDK version is 2.17.1.

Because test >=1.16.6 <1.17.10 depends on analyzer ^1.0.0 and test >=1.17.10 <1.20.0 depends on analyzer >=1.0.0 <3.0.0, test >=1.16.6 <1.20.0 requires analyzer >=1.0.0 <3.0.0.
And because test >=1.20.0 <1.21.0 depends on analyzer >=2.0.0 <4.0.0 and test >=1.21.5 requires SDK version >=2.18.0-146.0.dev <3.0.0, test >=1.16.6 <1.21.0-∞ or >=1.21.5 requires analyzer >=1.0.0 <4.0.0.
And because test >=1.21.4 <1.21.5 depends on test_core 0.4.16 and test >=1.21.3 <1.21.4 depends on test_core 0.4.15, test >=1.16.6 <1.21.0-∞ or >=1.21.3 requires analyzer >=1.0.0 <4.0.0 or test_core 0.4.15 or 0.4.16.
And because test >=1.21.2 <1.21.3 depends on test_core 0.4.14 and test >=1.21.0 <1.21.2 depends on test_core 0.4.13, test >=1.16.6 requires analyzer >=1.0.0 <4.0.0 or test_core 0.4.13 or 0.4.14 or 0.4.15 or 0.4.16.
And because build_runner >=2.2.1 depends on analyzer >=4.4.0 <6.0.0 and mockingjay >=0.2.0 depends on test ^1.17.0, if build_runner >=2.2.1 and mockingjay >=0.2.0 then test_core 0.4.13 or 0.4.14 or 0.4.15 or 0.4.16.
And because test_core >=0.3.23 <0.4.17 depends on frontend_server_client ^2.1.0 and build_runner >=2.3.1 depends on frontend_server_client ^3.0.0, build_runner >=2.3.1 is incompatible with mockingjay >=0.2.0.
So, because sofi_x_package depends on both build_runner ^2.3.2 and mockingjay ^0.3.0, version solving failed.
pub get failed (1; So, because sofi_x_package depends on both build_runner ^2.3.2 and mockingjay ^0.3.0, version solving failed.)

Additional context Downgrading to build_runner 2.2.1 acts a workaround

felangel commented 1 year ago

Hi @prolificcoder πŸ‘‹ This is a duplicate of https://github.com/flutter/flutter/issues/115284 and should be fixed on the Flutter master channel.