Replies: 2 comments
-
|
I have a workaround. If I remove my "dev_dependencies" for "bloc_test" in the project where I am adding my package to, then it works and I can just add the dependency again. Still there seems to be a bug here. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I don't believe it's a bug you have conflicting dependencies.
OnePub has nothing to do with the dependency resolution phase except to
allow the dart pub command to download the package.
…On Mon, 10 Feb 2025, 8:35 pm sneigaard, ***@***.***> wrote:
I have a workaround. If I remove my "dev_dependencies" for "bloc_test" in
the project where I am adding my package to, then it works and I can just
add the dependency again. Still there seems to be a bug here.
—
Reply to this email directly, view it on GitHub
<#550 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG32OGNGDPKKH5M5GXDAAT2PBXHHAVCNFSM6AAAAABW2BMGYCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJRGU3TOOA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have uploaded a package with success to OnePub and I have added my ONEPUB_TOKEN and I am trying to add a dependency to that uploaded package in another project with the
onepub pub add XXXcommand, but I get this error:OnePub version: 5.0.0
https://onepub.dev/api/fayhhnofly/
Because test >=1.25.9 depends on test_api 0.7.4 and test >=1.16.0-nullsafety.19 <1.16.6 depends on test_api 0.2.19, test >=1.16.0-nullsafety.19
<1.16.6-∞ or >=1.25.9 requires test_api 0.2.19 or 0.7.4.
And because every version of flutter_test from sdk depends on test_api 0.7.3, flutter_test from sdk is incompatible with test >=1.16.0-nullsafety.19
<1.16.6-∞ or >=1.25.9.
And because bloc_test >=8.0.0-nullsafety.5 depends on test ^1.16.0 and test >=1.24.4 <1.25.9 depends on analyzer >=5.12.0 <7.0.0, if flutter_test from
sdk and bloc_test >=8.0.0-nullsafety.5 then analyzer >=5.12.0 <7.0.0 or test >=1.16.6 <1.24.4.
And because test >=1.21.6 <1.24.4 depends on analyzer >=2.0.0 <6.0.0 and test >=1.21.0 <1.21.6 depends on analyzer >=2.0.0 <5.0.0, if flutter_test
from sdk and bloc_test >=8.0.0-nullsafety.5 then analyzer >=2.0.0 <7.0.0 or test >=1.16.6 <1.21.0.
And because test >=1.20.0 <1.21.0 depends on analyzer >=2.0.0 <4.0.0 and test >=1.17.10 <1.20.0 depends on analyzer >=1.0.0 <3.0.0, if flutter_test
from sdk and bloc_test >=8.0.0-nullsafety.5 then analyzer >=1.0.0 <7.0.0 or test >=1.16.6 <1.17.10.
And because test >=1.16.6 <1.17.10 depends on analyzer ^1.0.0 and copy_with_extension_gen >=6.0.1 depends on analyzer ^7.0.0, one of flutter_test from
sdk or bloc_test >=8.0.0-nullsafety.5 or copy_with_extension_gen >=6.0.1 must be false.
(1) So, because copy_with_extension_gen >=6.0.0 <6.0.1 depends on analyzer ^6.5.0 and analyzer >=6.5.0 <6.5.1 depends on macros >=0.1.0-main.0 <0.1.1, if
flutter_test from sdk and bloc_test >=8.0.0-nullsafety.5 and copy_with_extension_gen >=6.0.0 then macros >=0.1.0-main.0 <0.1.1 or analyzer ^6.5.1.
Anyone has experience the same and know how to fix this? Why does adding a dependency complain about other dependencies?
Beta Was this translation helpful? Give feedback.
All reactions