ExampleĪ simple but complete pubspec looks something like the following: That won’t clash with future pubspec fields. If you add a custom field, give it a unique name List of topics for the package.įor configuring the environment and managing assets. Specify a list of screenshot files to display Specify files to ignore when conducting a pre-publishing search List of URLs where users can sponsor development of the package. Used to explicitly declare supported platforms Used to put a package’s executables on your PATH. dependency_overrides Can be omitted if you do not need to override any dependencies. dev_dependencies Can be omitted if your package has no dev dependencies. dependencies Can be omitted if your package has no dependencies. URL pointing to documentation for the package. URL pointing to an issue tracker for the package.
#2.10 4 FLUTTER CODE#
URL pointing to the package’s source code repository.
URL pointing to the package’s homepage (or source code repository). description Required for packages that are hosted on the pub.dev site. version Required for packages that are hosted on the pub.dev site. Others also need to provide some other information so users can discover them.Īll of this metadata goes in the package’s pubspec:Ī file named pubspec.yaml that’s written in theĪ pubspec can have the following fields: name Required for every package. Every pub package needs some metadata so it can specify itsĭependencies.
0 kommentar(er)
