flavored_env 0.5.0 flavored_env: ^0.5.0 copied to clipboard
A utility to generate matching dotenv and dart configuration files.
We analyzed this package 33 hours ago, and awarded it 140 pub points (of a possible 160):
10/10 points: Provide a valid pubspec.yaml
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: MIT
.
0/10 points: 20% or more of the public API has dartdoc comments
0 out of 8 API elements (0.0 %) have documentation comments.
Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API. Document at least 20% of the public API elements.
To highlight public API members missing documentation consider enabling the public_member_api_docs
lint.
Some symbols that are missing documentation: flavored_env
, flavored_env.FlavoredEnvCommandRunner
, flavored_env.FlavoredEnvCommandRunner.FlavoredEnvCommandRunner
, flavored_env.FlavoredEnvCommandRunner.logger
, flavored_env.FlavoredEnvCommandRunner.parser
.
10/10 points: Package has an example
20/20 points: Supports 5 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
-
✓ Android
-
✓ iOS
-
✓ Windows
-
✓ Linux
-
✓ macOS
These platforms are not supported:
Package not compatible with platform Web
Because:
package:flavored_env/flavored_env.dart
that imports:package:flavored_env/src/flavored_env_command_runner.dart
that imports:package:pub_updater/pub_updater.dart
that imports:package:pub_updater/src/pub_updater.dart
that imports:package:process/process.dart
that imports:package:process/src/interface/process_wrapper.dart
that imports:dart:io
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:flavored_env/flavored_env.dart
that imports:package:flavored_env/src/flavored_env_command_runner.dart
that imports:package:pub_updater/pub_updater.dart
that imports:package:pub_updater/src/pub_updater.dart
that imports:package:process/process.dart
that imports:package:process/src/interface/process_wrapper.dart
that imports:dart:io
This package is not compatible with runtime wasm
, and will not be rewarded full points in a future version of the scoring model.
See https://dart.dev/web/wasm for details.
50/50 points: code has no errors, warnings, lints, or formatting issues
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
args |
^2.3.0 |
2.6.0 | 2.6.0 |
dart_style |
^2.2.1 |
2.3.7 | 2.3.7 |
logging |
^1.0.2 |
1.3.0 | 1.3.0 |
path |
^1.8.0 |
1.9.1 | 1.9.1 |
pub_updater |
^0.2.2 |
0.2.4 | 0.5.0 |
recase |
^4.0.0 |
4.1.0 | 4.1.0 |
yaml |
^3.1.0 |
3.1.2 | 3.1.2 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
_fe_analyzer_shared |
- | 73.0.0 | 76.0.0 |
_macros |
- | 0.3.2 | 0.3.2 |
analyzer |
- | 6.8.0 | 6.11.0 |
async |
- | 2.12.0 | 2.12.0 |
collection |
- | 1.19.1 | 1.19.1 |
convert |
- | 3.1.2 | 3.1.2 |
crypto |
- | 3.0.6 | 3.0.6 |
file |
- | 6.1.4 | 7.0.1 |
glob |
- | 2.1.2 | 2.1.2 |
http |
- | 0.13.6 | 1.2.2 |
http_parser |
- | 4.1.1 | 4.1.1 |
json_annotation |
- | 4.9.0 | 4.9.0 |
macros |
- | 0.1.2-main.4 | 0.1.3-main.0 |
meta |
- | 1.16.0 | 1.16.0 |
package_config |
- | 2.1.0 | 2.1.0 |
platform |
- | 3.1.6 | 3.1.6 |
process |
- | 4.2.4 | 5.0.2 |
pub_semver |
- | 2.1.4 | 2.1.4 |
source_span |
- | 1.10.0 | 1.10.0 |
string_scanner |
- | 1.4.0 | 1.4.0 |
term_glyph |
- | 1.2.1 | 1.2.1 |
typed_data |
- | 1.4.0 | 1.4.0 |
watcher |
- | 1.1.0 | 1.1.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^0.2.2` on pub_updater does not support the stable version `0.3.0`.
Try running dart pub upgrade --major-versions pub_updater
to update the constraint.
10/10 points: Package supports latest stable Dart and Flutter SDKs
20/20 points: Compatible with dependency constraint lower bounds
pub downgrade
does not expose any static analysis error.
Analyzed with Pana 0.22.13
, Dart 3.5.3
.
Check the analysis log for details.