-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
pub error messages should include more context #5971
Comments
This comment was originally written by jvande...@gmail.com I am still seeing this issue. I am running Version 0.1.6.r0013679, build 13679. The error does seem to indicate that there is something wrong with some packages dependency configuration. If that is the case I think the request is simply for a more clear error. |
This comment was originally written by jvande...@gmail.com Also this is what my project pub spec looks like. name: 'Project' |
Ah. I think what happened here is the version of "js" on google_maps used to be a "git" URL, whereas "web_components" used a hosted URL. I now get a slightly more sensible error: Package 'js' has disjoint constraints. |
also, the error messages could still be better :) it would be nice if, e.g. it printed what the disjoint constraints are and which pubspec's they came from |
FYI, web_components now accepts "any" JS interop version |
Added this to the M2 milestone. |
Yeah, we should definitely be more helpful here. |
Added Started label. |
Added Fixed label. |
Issue #7139 has been merged into this issue. |
Issue #7127 has been merged into this issue. |
This issue has been moved to dart-lang/pub#216. |
We got a bug report with an error:
Running pub update fails on web-components with the following message:
Package 'js' is depended on from both sources 'hosted' and 'git'.
I suspect the underlying bug was already fixed. But, it would be nice if the error message had printed more context. For example, which pubspec.yaml referred to it as "git" and which was "hosted"? We need something like a "stack trace" of dependencies to help users track down this kind of bug.
https://github.com/dart-lang/dart-web-components/issues/86
The text was updated successfully, but these errors were encountered: