isoos
commented
2 months ago Its because the package depends on package:macros, but does not depend on an SDK that supports that specific macros version:
Because macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk which doesn't match any versions, macros >=0.1.2-main.2 <0.1.2-main.4 is forbidden.
And because analyzer >=6.6.0 depends on macros >=0.1.2-main.3 <0.1.3 and macros >=0.1.2-main.4 depends on _macros 0.3.2 from sdk, analyzer >=6.6.0 requires _macros 0.3.2 from sdk.See https://github.com/dart-lang/pub-dev/issues/7597
/cc @jakemac53 @jonasfj
eernstg
jakemac53
jonasfj
I just published a new version of the package reflectable at https://pub.dev/packages/reflectable (version 4.0.7).
The scores are very low, because (apparently) the code doesn't pass static analysis.
However, no issues arise during static analysis locally:
dart pub get
``` > dart pub get Resolving dependencies... (1.1s) Downloading packages... + _fe_analyzer_shared 72.0.0 + _macros 0.3.1 from sdk dart + analyzer 6.7.0 + args 2.5.0 + async 2.11.0 + boolean_selector 2.1.1 + build 2.4.1 + build_config 1.1.1 + build_daemon 4.0.2 + build_resolvers 2.4.2 + build_runner 2.4.11 + build_runner_core 7.3.1 + build_test 2.2.2 + built_collection 5.1.1 + built_value 8.9.2 + checked_yaml 2.0.3 + code_builder 4.10.0 + collection 1.19.0 + convert 3.1.1 + coverage 1.8.0 + crypto 3.0.3 + csslib 1.0.0 + dart_style 2.3.6 + file 7.0.0 + fixnum 1.1.0 + frontend_server_client 4.0.0 + glob 2.1.2 + graphs 2.3.1 + html 0.15.4 + http_multi_server 3.2.1 + http_parser 4.1.0 + io 1.0.4 + js 0.7.1 + json_annotation 4.9.0 + lints 4.0.0 + logging 1.2.0 + macros 0.1.2-main.3 (0.1.2-main.4 available) + matcher 0.12.16+1 + meta 1.15.0 + mime 1.0.5 + node_preamble 2.0.2 + package_config 2.1.0 + path 1.9.0 + pool 1.5.1 + pub_semver 2.1.4 + pubspec_parse 1.3.0 + shelf 1.4.2 + shelf_packages_handler 3.0.2 + shelf_static 1.1.2 + shelf_web_socket 2.0.0 + source_map_stack_trace 2.1.1 + source_maps 0.10.12 + source_span 1.10.0 + stack_trace 1.11.1 + stream_channel 2.1.2 + stream_transform 2.1.0 + string_scanner 1.2.0 + term_glyph 1.2.1 + test 1.25.8 + test_api 0.7.3 + test_core 0.6.5 + timing 1.0.1 + typed_data 1.3.2 + vm_service 14.2.4 + watcher 1.1.0 + web 0.5.1 + web_socket 0.1.5 + web_socket_channel 3.0.0 + webkit_inspection_protocol 1.2.1 + yaml 3.1.2 Changed 70 dependencies! 1 package has newer versions incompatible with dependency constraints. Try `dart pub outdated` for more information. ```dart analyze lib
``` > dart analyze lib No issues found! ```dart pub upgrade
``` > dart pub upgrade Resolving dependencies... (1.1s) Downloading packages... macros 0.1.2-main.3 (0.1.2-main.4 available) No dependencies changed. 1 package has newer versions incompatible with dependency constraints. Try `dart pub outdated` for more information. ```dart pub outdated
``` > dart pub outdated Showing outdated packages. [*] indicates versions that are not the latest available. Package Name Current Upgradable Resolvable Latest direct dependencies: all up-to-date. dev_dependencies: all up-to-date. transitive dependencies: macros *0.1.2-main.3 *0.1.2-main.3 *0.1.2-main.3 0.1.2-main.4 all dependencies are up-to-date. ```Note in particular that
dart pub getreports "1 package has newer versions incompatible with dependency constraints", which wouldn't be the starting point for changing anything (we can't use that newer version). Moreover,dart pub upgradereportsall dependencies are up-to-date.But the 'Scores' page reports that
dart pub getfailed, the section 'Support up-to date dependencies says that "dart pub getfailed".In the log I can see this:
So why would Pana fail when
dart pub outdated(and other commands) locally do not report any issues that imply a need to make any changes?