We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
this came up on the mailing list, but I've noticed it myself too. If you forget to run "pub install" the error message is confusing:
Error: line 1 pos 1: library handler failed #import('package:unittest/unittest.dart');
The VM doesn't know about "pub" but maybe it could print something more like:
Error: line 1 pos 1: could not find library in the root packages directory, did you forget to install it? #import('package:unittest/unittest.dart');
That would give users a better idea of what went wrong and how to fix it.
A related issue: when one library import fails deep down, the VM reports a cascade of failures. It isn't immediately clear which one had the typo.
The text was updated successfully, but these errors were encountered:
Added this to the Later milestone.
Sorry, something went wrong.
Removed Priority-Medium label. Added Priority-Unassigned label.
Removed this from the Later milestone. Added Oldschool-Milestone-Later label.
Removed Oldschool-Milestone-Later label.
Assumed Stale
No branches or pull requests
this came up on the mailing list, but I've noticed it myself too. If you forget to run "pub install" the error message is confusing:
Error: line 1 pos 1: library handler failed
#import('package:unittest/unittest.dart');
The VM doesn't know about "pub" but maybe it could print something more like:
Error: line 1 pos 1: could not find library in the root packages directory, did you forget to install it?
#import('package:unittest/unittest.dart');
That would give users a better idea of what went wrong and how to fix it.
A related issue: when one library import fails deep down, the VM reports a cascade of failures. It isn't immediately clear which one had the typo.
The text was updated successfully, but these errors were encountered: