generated from nimblehq/git-template
-
Notifications
You must be signed in to change notification settings - Fork 4
/
pubspec.yaml
97 lines (87 loc) · 3.47 KB
/
pubspec.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
name: {{project_name.snakeCase()}}
description: A new Flutter project.
# The following line prevents the package from being accidentally published to
# pub.dev using `flutter pub publish`. This is preferred for private packages.
publish_to: 'none' # Remove this line if you wish to publish to pub.dev
# The following defines the version and build number for your application.
# A version number is three numbers separated by dots, like 1.2.43
# followed by an optional build number separated by a +.
# Both the version and the builder number may be overridden in flutter
# build by specifying --build-name and --build-number, respectively.
# In Android, build-name is used as versionName while build-number used as versionCode.
# Read more about Android versioning at https://developer.android.com/studio/publish/versioning
# In iOS, build-name is used as CFBundleShortVersionString while build-number is used as CFBundleVersion.
# Read more about iOS versioning at
# https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
# In Windows, build-name is used as the major, minor, and patch parts
# of the product and file versions while build-number is used as the build suffix.
version: {{app_version}}+{{build_number}}
environment:
sdk: '>=3.0.0 <4.0.0'
# Dependencies specify other packages that your package needs in order to work.
# To automatically upgrade your package dependencies to the latest versions
# consider running `flutter pub upgrade --major-versions`. Alternatively,
# dependencies can be manually updated by changing the version numbers below to
# the latest version available on pub.dev. To see which dependencies have newer
# versions available, run `flutter pub outdated`.
dependencies:
dio: ^5.1.2
equatable: ^2.0.5
flutter:
sdk: flutter
flutter_config: ^2.0.2
flutter_localizations:
sdk: flutter
flutter_riverpod: ^2.3.6
flutter_secure_storage: ^9.0.0
flutter_svg: ^2.0.7
freezed_annotation: ^2.2.0
get_it: ^7.6.0
go_router: ^9.0.3
injectable: ^2.1.2
intl: ^0.18.0
json_annotation: ^4.8.1
package_info_plus: ^4.0.0{{#add_permission_handler}}{{{ _pubspec_dependencyyaml }}}{{/add_permission_handler}}
retrofit: ^4.0.1
dev_dependencies:
build_runner: ^2.4.4
flutter_gen_runner: ^5.3.1
flutter_lints: ^2.0.1
flutter_test:
sdk: flutter
freezed: ^2.3.4
injectable_generator: ^2.1.6
integration_test:
sdk: flutter
json_serializable: ^6.6.2
mockito: ^5.4.0
retrofit_generator: ^7.0.0
# For information on the generic Dart part of this file, see the
# following page: https://dart.dev/tools/pub/pubspec
# The following section is specific to Flutter packages.
flutter:
generate: true
# The following line ensures that the Material Icons font is
# included with your application, so that you can use the icons in
# the material Icons class.
uses-material-design: true
# An image asset can refer to one or more resolution-specific "variants", see
# https://flutter.dev/assets-and-images/#resolution-aware
#
# For details regarding adding assets from package dependencies, see
# https://flutter.dev/assets-and-images/#from-packages
#
# For details regarding fonts from package dependencies,
# see https://flutter.dev/custom-fonts/#from-packages
assets:
- assets/
- assets/svg/
- assets/images/
- assets/fonts/
fonts:
- family: neuzeit
fonts:
- asset: assets/fonts/neuzeit.otf
flutter_gen:
integrations:
flutter_svg: true