Flutter Plugin Tools implements a CLI with various productivity tools for hosting multiple Flutter plugins in one github repository. It is mainly used by the flutter/plugins and flutter/flutterfire repositories. It was mainly written to facilitate testing on Travis for these repositories (see travis.yaml).
As an example, Flutter Plugin Tools allows you to:
In order to use the tools you need to enable them once by running the following command:
$ pub global activate flutter_plugin_tools
To use all features of
flutter_plugin_tools you'll need the following commands in your
pub(recommended: version from
clang-formatversion 5 (alternatively, you can provide the path via
$ pub global run flutter_plugin_tools <command> $ pub global run flutter_plugin_tools <command> --shardIndex 0 --shardCount 3
help to print a list of available commands.
The sharded example above divides the plugins into three shards
and executes the tool on the first shard (index 0).
Add this to your package's pubspec.yaml file:
dependencies: flutter_plugin_tools: ^0.0.12
You can install packages from the command line:
$ pub get
$ flutter packages get
Alternatively, your editor might support
pub get or
flutter packages get.
Check the docs for your editor to learn more.
|0.0.12||Jul 16, 2018|
|0.0.11||Jul 16, 2018|
|0.0.10+2||Jul 13, 2018|
|0.0.10||Jun 16, 2018|
|0.0.9||Jun 15, 2018|
|0.0.8||May 1, 2018|
|0.0.7||Apr 12, 2018|
|0.0.5||Jul 7, 2017|
|0.0.4||Jun 14, 2017|
|0.0.3||Jun 8, 2017|
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Aug 14, 2018, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
Detected platforms: Flutter, web, other
No platform restriction found in libraries.
dartdoc runs without any issues.
Changelog entries help clients to follow the progress in your code.
Package is pre-v1 release.
While there is nothing inherently wrong with versions of
0.*.*, it usually means that the author is still experimenting with the general direction of the API.
Maintain an example.
Create a short demo in the
example/ directory to show how to use this package. Common file name patterns include:
example.dart or you could also use
|Dart SDK||>=1.8.0 <3.0.0|