cli_repl 0.2.3
cli_repl: ^0.2.3 copied to clipboard
A simple library for creating CLI REPLs
We analyzed this package 20 hours ago, and awarded it 120 pub points (of a possible 140):
0/10 points: Provide a valid pubspec.yaml
The package description is too short.
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.
5/5 points: Provide a valid README.md
5/5 points: Provide a valid CHANGELOG.md
10/10 points: Use an OSI-approved license
Detected license: BSD-3-Clause
.
10/10 points: 20% or more of the public API has dartdoc comments
9 out of 13 API elements (69.2 %) have documentation comments.
Some symbols that are missing documentation: cli_repl
, Repl
, Repl
, alwaysValid
.
10/10 points: Package has an example
20/20 points: Supports 6 of 6 possible platforms (iOS, Android, Web, Windows, MacOS, Linux)
- ✓ Android
- ✓ iOS
- ✓ Windows
- ✓ Linux
- ✓ MacOS
- ✓ Web
40/50 points: code has no errors, warnings, lints, or formatting issues
INFO: Use the generic function type syntax in 'typedef's.
lib/cli_repl.dart:53:14
╷
53 │ typedef bool StatementValidator(String text);
│ ^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/cli_repl.dart
INFO: Empty catch block.
lib/src/repl_adapter/vm.dart:96:25
╷
96 │ } on StdinException {}
│ ^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/repl_adapter/vm.dart
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
async |
^2.5.0 |
2.11.0 | 2.11.0 |
js |
^0.6.3 |
0.6.7 | 0.6.7 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
collection |
- | 1.18.0 | 1.18.0 |
meta |
- | 1.11.0 | 1.11.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
10/10 points: Package supports latest stable Dart and Flutter SDKs
Analyzed with Pana 0.21.43
, Dart 3.2.1
.
Check the analysis log for details.