aliothx_vue 0.0.3 aliothx_vue: ^0.0.3 copied to clipboard
Package for web view interaction between vue and flutter.
We analyzed this package 10 days ago, and awarded it 120 pub points (of a possible 160):
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
0/10 points: Use an OSI-approved license
No license was recognized.
Consider using an OSI-approved license in the LICENSE
file to make it more accessible to the community.
0/10 points: 20% or more of the public API has dartdoc comments
OUT:
Documenting aliothx_vue...
Discovering libraries...
Linking elements...
Precaching local docs for 127452 elements...
Initialized dartdoc with 189 libraries
Generating docs for library aliothx_vue.dart from package:aliothx_vue/aliothx_vue.dart...
Generating docs for library main.dart from package:aliothx_vue/main.dart...
Documented 2 public libraries in 24.7 seconds
ERR:
warning: aliothx_vue has no library level documentation comments
from aliothx_vue: (file:///tmp/pana_PLZCRX/lib/main.dart:1:9)
error: file already written at "aliothx_vue/index.html"
for symbol aliothx_vue: (file:///tmp/pana_PLZCRX/lib/main.dart:1:9)
conflicting with file already generated by aliothx_vue: (file:///tmp/pana_PLZCRX/lib/aliothx_vue.dart:1:1)
Dartdoc generates a path and filename to write to for each symbol.
'aliothx_vue' conflicts with another symbol in the generated path, and
therefore can not be written out. Changing the name, library name, or
class name (if appropriate) of one of the conflicting items can resolve
the conflict. Alternatively, use the @nodoc
directive in one symbol's
[16 more lines]
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
These issues are present but do not affect the score, because they may not originate in your package:
Package not compatible with platform Web
Because:
package:aliothx_vue/aliothx_vue.dart
that imports:package:logger/logger.dart
that imports:package:logger/src/outputs/advanced_file_output_stub.dart
that imports:dart:io
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:aliothx_vue/aliothx_vue.dart
that imports:package:logger/logger.dart
that imports:package:logger/src/outputs/advanced_file_output_stub.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 |
---|---|---|---|
dio |
^4.0.0 |
4.0.6 | 5.7.0 |
flutter |
flutter |
0.0.0 | 0.0.0 |
logger |
^2.0.2 |
2.5.0 | 2.5.0 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
characters |
- | 1.3.0 | 1.4.0 |
collection |
- | 1.19.0 | 1.19.1 |
http_parser |
- | 4.1.1 | 4.1.1 |
material_color_utilities |
- | 0.11.1 | 0.12.0 |
meta |
- | 1.15.0 | 1.16.0 |
path |
- | 1.9.1 | 1.9.1 |
sky_engine |
- | 0.0.0 | 0.0.0 |
source_span |
- | 1.10.1 | 1.10.1 |
string_scanner |
- | 1.4.1 | 1.4.1 |
term_glyph |
- | 1.2.2 | 1.2.2 |
typed_data |
- | 1.4.0 | 1.4.0 |
vector_math |
- | 2.1.4 | 2.1.4 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^4.0.0` on dio does not support the stable version `5.0.0`.
Try running dart pub upgrade --major-versions dio
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.17
, Flutter 3.27.0
, Dart 3.6.0
.
Check the analysis log for details.