There should be section about checking your package before publishing it using pana #6074
Labels
d.enhancement
Improves docs with specific ask
dev.packages
Relates to package publishing
e1-hours
Can complete in < 8 hours of normal, not dedicated, work
from.page-issue
Reported in a reader-filed concern
p3-low
Valid but not urgent concern. Resolve when possible. Encourage upvote to surface.
Page URL
https://dart.dev/tools/pub/publishing/
Page source
https://github.com/dart-lang/site-www/tree/main/src/content/tools/pub/publishing.md
Describe the problem
I went looking for the pana tool because I couldn't remember what it was called. I wanted to check my package before I published it to ensure I had a high pub points score, that I was reporting all of the platforms that were supported, I had good API docs coverage, etc.
Expected fix
there should be docs that encourage folks to use pana on their package before they publish it; they'll catch all kinds of errors that way and save them from getting errors that kick their package back or being surprised as to what pub.dev says about their package.
Additional context
pana is essentially a pre-publishing tool for package authors and we should be recommending everyone use it as part of their publishing process. and it's owned and maintained by the Dart Tools team, so there's no excuse for us not to encourage folks to use it.
I would like to fix this problem.
note: please excuse the use of the term "we" to imply my inclusion in the Dart/Flutter team. I still think of myself that way. : )
The text was updated successfully, but these errors were encountered: