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
If the activation intentionally fails, then maybe the flutter pub global activate output should warn of this. Based on this, it appears that the activation has occurred successfully:
~/ flutter pub global activate --source path ~/develop/devtools/packages/devtools_extensions/
Resolving dependencies in /Users/kenzieschmoll/develop/devtools/packages/devtools_extensions/...
! devtools_app_shared 0.0.1 from path develop/devtools/packages/devtools_app_shared (overridden)
! devtools_shared 3.0.0 from path develop/devtools/packages/devtools_shared (overridden)
material_color_utilities 0.5.0 (0.8.0 available)
Got dependencies in /Users/kenzieschmoll/develop/devtools/packages/devtools_extensions/!
Package devtools_extensions is currently active at path "/Users/kenzieschmoll/develop/devtools/packages/devtools_extensions".
Activated devtools_extensions 0.0.3-wip at path "/Users/kenzieschmoll/develop/devtools/packages/devtools_extensions".
It'll simply say:
Example: flutter/devtools#6259
Maybe this is more of a feature request than a bug really. But it explains why people might need to make
_cli
packages in some cases.The text was updated successfully, but these errors were encountered: