Skip to content
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

path version conflict #77

Closed
passsy opened this issue May 5, 2020 · 5 comments · Fixed by #84
Closed

path version conflict #77

passsy opened this issue May 5, 2020 · 5 comments · Fixed by #84

Comments

@passsy
Copy link
Collaborator

passsy commented May 5, 2020

dartx: 0.4.0 is incompatible with Flutter 1.17 because of path.

dependencies:
  flutter:
    sdk: flutter
  dartx: ^0.4.0

dev_dependencies:
  flutter_test:
    sdk: flutter
$ flutter packages get
Because every version of flutter_test from sdk depends on path 1.6.4 and dartx 0.4.0 depends on path ^1.7.0, flutter_test from sdk is incompatible with dartx 0.4.0.
And because no versions of dartx match >0.4.0 <0.5.0, flutter_test from sdk is incompatible with dartx ^0.4.0.
So, because spitch depends on both dartx ^0.4.0 and flutter_test any from sdk, version solving failed.
@passsy
Copy link
Collaborator Author

passsy commented May 5, 2020

The version range can't be expanded to include earlier versions of path because dartx depends on the new extension(String path, [int level]) method added to path: 1.7.0.

Workaround 1

For most users it should be fine to override the path dependency:

dependency_overrides:
  path: ^1.7.0

Some methods of the dartx_io libraries won't work but the rest does flawless.

Workaround 2

Upgrade to Flutter 1.18

Flutter already upgraded to path: 1.7.0. Every version after 1.18.0-6.0.pre works. I.e. dev channel which is currently at 1.18.0-8.0.pre.

@mreichelt
Copy link
Contributor

Yep, I'm affected by this. Wouldn't it make more sense to create regular versions for stable, and -dev or -beta versions for those who use Flutter Dev or Beta? It's kind of weird to force users into using builds not marked as stable.

@shinayser
Copy link
Contributor

Flutter 1.18 is the one that is being promoted to stable soon? I think it's the 1.17 right?

If it's the 1.17 the workaround 2 will not be possible for quite some time (until the next release I believe).

@passsy
Copy link
Collaborator Author

passsy commented May 6, 2020

Flutter 1.17 is the next stable version

@passsy
Copy link
Collaborator Author

passsy commented May 14, 2020

dartx: ^0.4.1 is now compatible with Flutter 1.17 (stable)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants