Dart CLI Packager
This package provides a set of Grinder tasks that make it easy to release a
Dart command-line application on many different release channels, to Dart users
and non-Dart users alike. It also integrates with Travis CI to make it easy to
automatically deploy packages.
To use this package, import package:cli_pkg/cli_pkg.dart and call
pkg.addAllTasks() before calling grind():
import 'package:cli_pkg/cli_pkg.dart' as pkg;
import 'package:grinder/grinder.dart';
void main(List<String> args) {
pkg.addAllTasks();
grind(args);
}
The following sets of tasks are provided, each of which can also be enabled
individually:
It's strongly recommended that this package be imported with the prefix pkg.
Configuration
This package is highly configurable, using ConfigVariable fields defined
at the top level of the library. By default, it infers as much configuration
as possible from the package's pubspec, but almost all properties can be
overridden in the main() method:
import 'package:cli_pkg/cli_pkg.dart' as pkg;
import 'package:grinder/grinder.dart';
void main(List<String> args) {
pkg.name.value = "bot-name";
pkg.humanName.value = "My App";
pkg.addAllTasks();
grind(args);
}
ConfigVariables whose values are expensive to compute or that might fail under
some circumstances can also be set to callback functions, which are called
lazily when the variables are used by the Grinder tasks:
import 'package:cli_pkg/cli_pkg.dart' as pkg;
import 'package:grinder/grinder.dart';
void main(List<String> args) {
pkg.githubReleaseNotes.fn = () => File.read("RELNOTES.md");
pkg.addAllTasks();
grind(args);
}
Each task describes exactly which configuration variables it uses. Configuration
that just applies to one set of tasks is always prefixed with a corresponding
name. For example, pkg.jsFlags applies to JavaScript compilation.
