activout_firebase_options_selector 1.0.0 activout_firebase_options_selector: ^1.0.0 copied to clipboard
When you have multiple Firebase projects for production, test and development, use this library to make it easier to switch between environments without building separate apps!
We analyzed this package 23 hours ago, and awarded it 150 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: MIT
.
10/10 points: 20% or more of the public API has dartdoc comments
13 out of 13 API elements (100.0 %) have documentation comments.
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
-
✓ macOS
-
✓ Web
These platforms are not supported:
Package does not support platform `Linux`.
Because:
package:activout_firebase_options_selector/activout_firebase_options_selector.dart
that imports:package:activout_firebase_options_selector/src/firebase_options_selector_dialog.dart
that imports:package:activout_firebase_options_selector/src/firebase_options_selector.dart
that imports:package:firebase_core/firebase_core.dart
that declares support for platforms:Android
,iOS
,Windows
,macOS
,Web
.
0/0 points: WASM compatibility
This package is compatible with runtime wasm
, and will be rewarded additional 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 |
---|---|---|---|
firebase_core |
^2.2.0 |
2.32.0 | 3.10.0 |
flutter |
flutter |
0.0.0 | 0.0.0 |
shared_preferences |
^2.0.15 |
2.3.5 | 2.3.5 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
async |
- | 2.11.0 | 2.12.0 |
boolean_selector |
- | 2.1.1 | 2.1.2 |
characters |
- | 1.3.0 | 1.4.0 |
clock |
- | 1.1.1 | 1.1.2 |
collection |
- | 1.19.0 | 1.19.1 |
fake_async |
- | 1.3.1 | 1.3.2 |
ffi |
- | 2.1.3 | 2.1.3 |
file |
- | 7.0.1 | 7.0.1 |
firebase_core_platform_interface |
- | 5.4.0 | 5.4.0 |
firebase_core_web |
- | 2.19.0 | 2.19.0 |
flutter_test |
- | 0.0.0 | 0.0.0 |
flutter_web_plugins |
- | 0.0.0 | 0.0.0 |
leak_tracker |
- | 10.0.7 | 10.0.8 |
leak_tracker_flutter_testing |
- | 3.0.8 | 3.0.9 |
leak_tracker_testing |
- | 3.0.1 | 3.0.1 |
matcher |
- | 0.12.16+1 | 0.12.17 |
material_color_utilities |
- | 0.11.1 | 0.12.0 |
meta |
- | 1.15.0 | 1.16.0 |
path |
- | 1.9.0 | 1.9.1 |
path_provider_linux |
- | 2.2.1 | 2.2.1 |
path_provider_platform_interface |
- | 2.1.2 | 2.1.2 |
path_provider_windows |
- | 2.3.0 | 2.3.0 |
platform |
- | 3.1.6 | 3.1.6 |
plugin_platform_interface |
- | 2.1.8 | 2.1.8 |
shared_preferences_android |
- | 2.4.0 | 2.4.0 |
shared_preferences_foundation |
- | 2.5.4 | 2.5.4 |
shared_preferences_linux |
- | 2.4.1 | 2.4.1 |
shared_preferences_platform_interface |
- | 2.4.1 | 2.4.1 |
shared_preferences_web |
- | 2.4.2 | 2.4.2 |
shared_preferences_windows |
- | 2.4.1 | 2.4.1 |
sky_engine |
- | 0.0.0 | 0.0.0 |
source_span |
- | 1.10.0 | 1.10.1 |
stack_trace |
- | 1.12.0 | 1.12.1 |
stream_channel |
- | 2.1.2 | 2.1.4 |
string_scanner |
- | 1.3.0 | 1.4.1 |
term_glyph |
- | 1.2.1 | 1.2.2 |
test_api |
- | 0.7.3 | 0.7.4 |
vector_math |
- | 2.1.4 | 2.1.4 |
vm_service |
- | 14.3.0 | 15.0.0 |
web |
- | 1.1.0 | 1.1.0 |
xdg_directories |
- | 1.1.0 | 1.1.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^2.2.0` on firebase_core does not support the stable version `3.0.0`.
Try running dart pub upgrade --major-versions firebase_core
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.1
, Dart 3.6.0
.
Check the analysis log for details.