dependencies_ field_ not_ map
Details about the 'dependencies_field_not_map' diagnostic produced by the Dart analyzer.
The value of the '{0}' field is expected to be a map.
Description
#
The analyzer produces this diagnostic when the value of either the
dependencies or dev_dependencies key isn't a map.
Example
#
The following code produces this diagnostic because the value of the
top-level dependencies key is a list:
name: example
dependencies:
- meta
Common fixes
#Use a map as the value of the dependencies key:
name: example
dependencies:
meta: ^1.0.2
Unless stated otherwise, the documentation on this site reflects Dart 3.10.3. Report an issue.