hetu_script_dev_tools 0.1.0+1 hetu_script_dev_tools: ^0.1.0+1 copied to clipboard
Extensions for Hetu Script dart package. Includes file system resource context helper class and command line REPL for Hetu Script.
We analyzed this package 3 days ago, and awarded it 90 pub points (of a possible 160):
0/10 points: Provide a valid pubspec.yaml
Failed to verify repository URL.
Please provide a valid repository
URL in pubspec.yaml
, such that:
repository
can be cloned,- a clone of the repository contains a
pubspec.yaml
, which:,- contains
name: hetu_script_dev_tools
, - contains a
version
property, and, - does not contain a
publish_to
property.
- contains
packages/hetu_script_dev_tools/pubspec.yaml
from the repository defines publish_to
, thus, we are unable to verify the package is published from here.
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
.
10/10 points: 20% or more of the public API has dartdoc comments
13 out of 48 API elements (27.1 %) have documentation comments.
Some symbols that are missing documentation: extension
, extension.HTExtension
, extension.HTExtension.loadModuleConsole
, extension_bindings
, extension_bindings.HTConsoleClass
.
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:hetu_script_dev_tools/hetu_script_dev_tools.dart
that imports:package:hetu_script_dev_tools/extensions/extension.dart
that imports:package:hetu_script_dev_tools/extensions/extension_bindings.dart
that imports:dart:io
0/0 points: WASM compatibility
Unable to detect compatibility with runtime wasm
, and this package will not be rewarded full points in a future version of the scoring model.
See https://dart.dev/web/wasm for details.
0/50 points: code has no errors, warnings, lints, or formatting issues
Found 6 issues. Showing the first 2:
ERROR: The named parameter 'debugPerformance' isn't defined.
bin/cli_tool.dart:36:7
╷
36 │ debugPerformance: false,
│ ^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze bin/cli_tool.dart
ERROR: The named parameter 'compileWithoutLineInfo' isn't defined.
bin/cli_tool.dart:37:7
╷
37 │ compileWithoutLineInfo: true,
│ ^^^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze bin/cli_tool.dart
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
args |
^2.1.0 |
2.6.0 | 2.6.0 |
hetu_script |
^0.4.1+1 |
0.4.2+1 | 0.4.2+1 |
http |
^0.13.4 |
0.13.6 | 1.2.2 |
path |
^1.8.0 |
1.9.1 | 1.9.1 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
async |
- | 2.12.0 | 2.12.0 |
boolean_selector |
- | 2.1.2 | 2.1.2 |
characters |
- | 1.3.1 | 1.3.1 |
clock |
- | 1.1.2 | 1.1.2 |
collection |
- | 1.19.1 | 1.19.1 |
fast_noise |
- | 1.0.1 | 2.0.0 |
fixnum |
- | 1.1.1 | 1.1.1 |
http_parser |
- | 4.1.1 | 4.1.1 |
intl |
- | 0.17.0 | 0.20.0 |
matcher |
- | 0.12.17 | 0.12.17 |
meta |
- | 1.16.0 | 1.16.0 |
pub_semver |
- | 2.1.4 | 2.1.4 |
quiver |
- | 3.2.2 | 3.2.2 |
recase |
- | 4.1.0 | 4.1.0 |
source_span |
- | 1.10.0 | 1.10.0 |
stack_trace |
- | 1.12.0 | 1.12.0 |
stream_channel |
- | 2.1.2 | 2.1.2 |
string_scanner |
- | 1.4.0 | 1.4.0 |
term_glyph |
- | 1.2.1 | 1.2.1 |
test_api |
- | 0.7.3 | 0.7.3 |
typed_data |
- | 1.4.0 | 1.4.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^0.13.4` on http does not support the stable version `1.0.0`.
Try running dart pub upgrade --major-versions http
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.15
, Dart 3.5.4
.
Check the analysis log for details.