event_loop_watchdog 0.1.0+1 event_loop_watchdog: ^0.1.0+1 copied to clipboard
A Dart package to help detect whenever your main `event loop` is blocked.
We analyzed this package 17 hours ago, and awarded it 120 pub points (of a possible 140):
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
3 out of 18 API elements (16.7 %) 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.
Some symbols that are missing documentation: event_loop_watchdog
, event_loop_watchdog.Action.run
, event_loop_watchdog.ActionCreator
, event_loop_watchdog.NullAction.run
, event_loop_watchdog.StackTraceAction.createStackTraceAction
.
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:event_loop_watchdog/event_loop_watchdog.dart
that imports:package:vm_service/vm_service_io.dart
that imports:dart:io
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 |
---|---|---|---|
path |
^1.8.3 |
1.9.0 | 1.9.0 |
vm_service |
^11.9.0 |
11.10.0 | 14.2.1 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^11.9.0` on vm_service does not support the stable version `12.0.0`.
Try running dart pub upgrade --major-versions vm_service
to update the constraint.
10/10 points: Package supports latest stable Dart and Flutter SDKs
Analyzed with Pana 0.22.3
, Dart 3.3.4
.
Check the analysis log for details.