-
Notifications
You must be signed in to change notification settings - Fork 0
/
pubspec.yaml
102 lines (90 loc) · 3.66 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
98
99
100
101
102
name: chatai
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: 1.0.0+1
environment:
sdk: '>=2.7.0 <3.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:
flutter:
sdk: flutter
cupertino_icons: ^1.0.5
shared_preferences: ^2.0.17
flutter_spinkit: ^5.1.0
connectivity_plus: ^3.0.2
provider: ^6.0.5
http: ^0.13.5
lottie: ^2.2.0
material_design_icons_flutter: 6.0.7096
package_info_plus: ^3.0.2
velocity_x: ^3.6.0
introduction_screen: ^3.1.4
flutter_svg: ^1.1.6
text_to_speech: ^0.2.3
clipboard: ^0.1.3
flutter_share: ^2.0.0
rflutter_alert: ^2.0.4
url_launcher: ^6.1.8
animated_text_kit: ^4.2.2
# google_mobile_ads: ^2.3.0
google_mobile_ads: ^3.0.0
easy_ads_flutter: ^2.0.1
# in_app_purchase: ^3.1.1
flutter_local_notifications: ^13.0.0
# flutter_timezone: ^1.0.7
timezone: ^0.9.1
# purchases_flutter: ^4.9.1
rate_my_app: ^1.1.3
flutter_email_sender: ^5.2.0
double_back_to_close_app: ^2.1.0
restart_app: ^1.1.2
dev_dependencies:
flutter_test:
sdk: flutter
# The "flutter_lints" package below contains a set of recommended lints to
# encourage good coding practices. The lint set provided by the package is
# activated in the `analysis_options.yaml` file located at the root of your
# package. See that file for information about deactivating specific lint
# rules and activating additional ones.
flutter_lints: ^2.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:
# 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
assets:
- assets/images/
- assets/json/
fonts:
- family: PT_Sans
fonts:
- asset: fonts/PT_Sans/PTSans-Italic.ttf
weight: 100
- asset: fonts/PT_Sans/PTSans-Regular.ttf
weight: 300
- asset: fonts/PT_Sans/PTSans-BoldItalic.ttf
weight: 400
- asset: fonts/PT_Sans/PTSans-Bold.ttf
weight: 500