celest_cloud 0.1.4

celest_cloud: ^0.1.4 copied to clipboard

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-Patent.

0/10 points: 20% or more of the public API has dartdoc comments

Dependency resolution failed, unable to run dartdoc.

0/10 points: Package has an example

0/20 points: Platform support detection failed

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

• Running dart pub outdated failed with the following output:

Because celest_cloud depends on celest_core >=0.3.0-dev.1 which requires the Flutter SDK, version solving failed.
Flutter users should use `flutter pub` instead of `dart pub`.

0/10 points: All of the package dependencies are supported in the latest version

• Could not run dart pub outdated: dart pub get failed:

OUT:
Resolving dependencies...
ERR:
Because celest_cloud depends on celest_core >=0.3.0-dev.1 which requires the Flutter SDK, version solving failed.

Flutter users should use `flutter pub` instead of `dart pub`.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on celest_core: dart pub add celest_core:^0.2.1

10/10 points: Package supports latest stable Dart and Flutter SDKs

0/20 points: Compatible with dependency constraint lower bounds

dart pub downgrade failed with:

OUT:
Resolving dependencies...
ERR:
Because celest_cloud depends on celest_core >=0.3.0-dev.1 which requires the Flutter SDK, version solving failed.

Flutter users should use `flutter pub` instead of `dart pub`.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on celest_core: dart pub add celest_core:^0.0.3

Run dart pub downgrade and then dart analyze to reproduce the above problem.

You may run dart pub upgrade --tighten to update your dependency constraints, see dart.dev/go/downgrade-testing for details.