Skip to content

Ensure up-to-date dependencies #58

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

Closed
matanlurey opened this issue May 30, 2018 · 1 comment
Closed

Ensure up-to-date dependencies #58

matanlurey opened this issue May 30, 2018 · 1 comment

Comments

@matanlurey
Copy link
Contributor

Blocking angulardart/angular#1095.

It's incredibly easy to use an out-of-date set of build_runner, build_web_compilers, and build_test - which, coupled with dart-lang/pub#912, means that users frequently use out of date development dependencies, and when they try and upgrade, hit deadlocks or incomprehensible error messages, i.e (as an example only):

Resolving dependencies...
Package angular_components has no versions that match >=0.9.0-alpha+8 <0.10.0 derived from:
- merck_crm_mashup depends on version ^0.9.0-alpha+8
Process finished with exit code 1

An alternative would be support for peer_dependencies in pub: dart-lang/pub#1837.

@grouma
Copy link
Member

grouma commented Apr 22, 2019

Closing as there is no work for us to do.

We have logic to ensure that the required build_runner, build_web_compilers and even build_daemon packages are used. With the recent changes to pub, the errors are not as cryptic.

I agree in an ideal world we would make use of peer_dependencies but I don't think those are coming any time soon..

@grouma grouma closed this as completed Apr 22, 2019
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

No branches or pull requests

2 participants