You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During lengthy projects, it is impossible to always use the latest version of every package. Installing a new latest package usually runs into version solving errors :
Because package_name >=5.0.0-nullsafety.0 depends on platform ^3.0.0 and package_name 6.0.16 depends on platform ^2.0.0, package_name >=5.0.0-nullsafety.0 is incompatible with package_name 6.0.16.
And because no versions of package_name match >6.0.16 <7.0.0, package_name >=5.0.0-nullsafety.0 is incompatible with package_name ^6.0.16.
So, because project_name depends on both package_name ^6.0.16 and package_name ^5.0.0+1, version solving failed.
pub get failed (1; So, because project_name depends on both package_name ^6.0.16 and package_name ^5.0.0+1, version solving failed.)
exit code 1
Install the latest dependency that is compatible with all other packages (or install the latest package and give a prompt asking the user whether to install the older (compatible) version).
An option to enter the exact version in the search bar. Like sqflite: ^2.0.0+3.
An option to upgrade all packages to latest version (best if all upgraded to the latest compatible versions).
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion! I'd welcome a feature like this to Pubspec Assist! I'll have to see when this can be implemented, especially considering there are already great tools to do this for you.
One example is lockpick, a CLI (that I made, full disclosure) that aims to solve these problems. Let me know if this works for you! In the meantime, I'll keep this issue open to track potential progress.
During lengthy projects, it is impossible to always use the latest version of every package. Installing a new latest package usually runs into version solving errors :
sqflite: ^2.0.0+3
.The text was updated successfully, but these errors were encountered: