The README already says it: "Not on pub.dev yet, so install it from git". That instruction is four lines of shell and a PATH change, which is enough friction to lose most of the people who would otherwise try it.
Why it matters
pub.dev is where Flutter and Dart developers look. A package there is one dart pub global activate binary_sdk_bridge away, appears in pub.dev search, gets an automatically generated API docs page, and carries a score that signals whether it is maintained.
The current install path also means nobody can pin a version.
Before publishing
Ordering
#4 and #10 both cover the CLI having no tests. Publishing a CLI whose exit codes are unverified is the wrong order, so those probably come first.
Note
pub.dev publication cannot be undone. A version can be retracted, but the package name is permanent.
The README already says it: "Not on pub.dev yet, so install it from git". That instruction is four lines of shell and a
PATHchange, which is enough friction to lose most of the people who would otherwise try it.Why it matters
pub.dev is where Flutter and Dart developers look. A package there is one
dart pub global activate binary_sdk_bridgeaway, appears in pub.dev search, gets an automatically generated API docs page, and carries a score that signals whether it is maintained.The current install path also means nobody can pin a version.
Before publishing
dart pub publish --dry-runpassestopics:inpubspec.yaml, which is pub.dev's main discovery mechanismexample/directory, sincepanascores it and it is the first thing people openOrdering
#4 and #10 both cover the CLI having no tests. Publishing a CLI whose exit codes are unverified is the wrong order, so those probably come first.
Note
pub.dev publication cannot be undone. A version can be retracted, but the package name is permanent.