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
2.The installing tab on the pub package site should be adaptable by the author. So instead of adding the AP to the dependencies and importing it, we should see eg. download the package to your drive and run ###.dart.
currently I use the readme which might confuse people since they might think they have to do both installations.
additionally it would be awesome
3.Since the AP is not listed inside a pubspec file, there is no update functionality for the package (except if the user works with the bleeding edge git repo or would it work with path too?)
Thank you
The text was updated successfully, but these errors were encountered:
Pub's support for packages that expose binaries is still mostly non-existent. Once that's further along, the publishing experience will be adapted to support them better too.
Added Duplicate label. Marked as being merged into #7874.
This issue was originally filed by [email protected]
It seems that application packages(AP) are treated as lib packages by pub.
http://stackoverflow.com/questions/17553846/if-and-how-to-publish-application-packages-to-pub
1.AP needs a lib folder in order to be published.
2.The installing tab on the pub package site should be adaptable by the author. So instead of adding the AP to the dependencies and importing it, we should see eg. download the package to your drive and run ###.dart.
currently I use the readme which might confuse people since they might think they have to do both installations.
additionally it would be awesome
3.Since the AP is not listed inside a pubspec file, there is no update functionality for the package (except if the user works with the bleeding edge git repo or would it work with path too?)
Thank you
The text was updated successfully, but these errors were encountered: