conduit_runtime 3.2.11
conduit_runtime: ^3.2.11 copied to clipboard
Provides behaviors and base types for packages that can use mirrors and be AOT compiled.
We analyzed this package 21 days ago, and awarded it 130 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: BSD-2-Clause.
10/10 points: 20% or more of the public API has dartdoc comments
29 out of 107 API elements (27.1 %) have documentation comments.
Some symbols that are missing documentation: runtime, runtime.Build, runtime.Build.Build.new, runtime.Build.compile, runtime.Build.context.
0/10 points: Package has an example
No example found.
See package layout guidelines on how to add an example.
20/20 points: Supports 3 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
-
✓ Windows
-
✓ Linux
-
✓ macOS
These platforms are not supported:
Package not compatible with platform Android
Because:
package:conduit_runtime/runtime.dartthat imports:package:conduit_runtime/src/mirror_coerce.dartthat imports:dart:mirrors
Package not compatible with platform iOS
Because:
package:conduit_runtime/runtime.dartthat imports:package:conduit_runtime/src/mirror_coerce.dartthat imports:dart:mirrors
Package not compatible with platform Web
Because:
package:conduit_runtime/runtime.dartthat imports:package:conduit_runtime/src/mirror_coerce.dartthat imports:dart:mirrors
40/50 points: code has no errors, warnings, lints, or formatting issues
Found 10 issues. Showing the first 2:
INFO: 'name' is deprecated and shouldn't be used. Use importPrefix, name2, and element instead.
lib/src/analyzer.dart:105:51
╷
105 │ .where((c) => c.extendsClause?.superclass.name.name == superclassName)
│ ^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/analyzer.dart
INFO: Missing a required trailing comma.
lib/src/build.dart:23:5
╷
23 │ };
│ ^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/build.dart
0/10 points: All of the package dependencies are supported in the latest version
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
analyzer |
^5.1.0 |
5.13.0 | 9.0.0 | |
args |
^2.0.0 |
2.7.0 | 2.7.0 | |
conduit_isolate_exec |
^3.2.11 |
3.2.11 | 6.0.0 | |
io |
^1.0.3 |
1.0.5 | 1.0.5 | |
package_config |
^2.1.0 |
2.2.0 | 2.2.0 | |
path |
^1.8.0 |
1.9.1 | 1.9.1 | |
pubspec |
^2.0.1 |
2.3.0 | 2.3.0 | Discontinued |
yaml |
^3.1.0 |
3.1.3 | 3.1.3 |
Transitive dependencies
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
_fe_analyzer_shared |
- | 61.0.0 | 92.0.0 | |
async |
- | 2.13.0 | 2.13.0 | |
boolean_selector |
- | 2.1.2 | 2.1.2 | |
collection |
- | 1.19.1 | 1.19.1 | |
convert |
- | 3.1.2 | 3.1.2 | |
crypto |
- | 3.0.7 | 3.0.7 | |
file |
- | 7.0.1 | 7.0.1 | |
glob |
- | 2.1.3 | 2.1.3 | |
matcher |
- | 0.12.18 | 0.12.18 | |
meta |
- | 1.17.0 | 1.17.0 | |
pub_semver |
- | 2.2.0 | 2.2.0 | |
quiver |
- | 3.2.2 | 3.2.2 | |
source_span |
- | 1.10.1 | 1.10.1 | |
stack_trace |
- | 1.12.1 | 1.12.1 | |
stream_channel |
- | 2.1.4 | 2.1.4 | |
string_scanner |
- | 1.4.1 | 1.4.1 | |
term_glyph |
- | 1.2.2 | 1.2.2 | |
test_api |
- | 0.7.8 | 0.7.8 | |
typed_data |
- | 1.4.0 | 1.4.0 | |
uri |
- | 1.0.0 | 1.0.0 | |
watcher |
- | 1.2.0 | 1.2.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides.
Found 3 issues. Showing the first 2:
The constraint `^5.1.0` on analyzer does not support the stable version `6.0.0`.
Try running dart pub upgrade --major-versions analyzer to update the constraint.
The constraint `^3.2.11` on conduit_isolate_exec does not support the stable version `4.0.0`.
Try running dart pub upgrade --major-versions conduit_isolate_exec 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.23.3, Dart 3.10.4.
Check the analysis log for details.