Use this package as a library
1. Depend on it
Add this to your package's pubspec.yaml file:
dependencies: libutil: ^0.0.3
2. Install it
You can install packages from the command line:
$ pub get
$ flutter pub get
Alternatively, your editor might support
pub get or
flutter pub get.
Check the docs for your editor to learn more.
3. Import it
Now in your Dart code, you can use:
import 'package:libutil/ansi.dart'; import 'package:libutil/communiation.dart'; import 'package:libutil/equality.dart'; import 'package:libutil/logging.dart'; import 'package:libutil/sorted.dart';
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 Oct 16, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
- Dart: 2.5.1
- pana: 0.12.21
Detected platforms: Flutter, other
Platform components identified in package:
dartfmt to format
Maintenance issues and suggestions
Provide a file named
README.md. (-30 points)
README.md file should inform others about your project, what it does, and how they can use it. See the example generated by
Provide a file named
CHANGELOG.md. (-20 points)
Changelog entries help developers follow the progress of your package. See the example generated by
Homepage URL doesn't exist. (-20 points)
At the time of the analysis the
https://inkable.io was unreachable.
The package description is too short. (-15 points)
Add more detail to the
description field of
pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.
Maintain an example. (-10 points)
Create a short demo in the
example/ directory to show how to use this package.
Common filename patterns include
libutil.dart. Packages with multiple examples should provide
For more information see the pub package layout conventions.
Package is pre-v0.1 release. (-10 points)
While nothing is inherently wrong with versions of
0.0.*, it might mean that the author is still experimenting with the general direction of the API.