You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| `analyze` | _see `flutter help analyze`_ | Analyze the project's Dart code |
139
-
| `assemble` | _see `flutter help assemble`_ | Assemble and build Flutter resources |
140
-
| `attach` | _see `flutter help attach`_ | Attach to a running app |
141
-
| `build-aar` | _see `flutter help build aar`_ | Build a repository containing an AAR and a POM file |
142
-
| `build-apk` | _see `flutter help build apk`_ | Build an Android APK file from your app |
143
-
| `build-appbundle` | _see `flutter help build appbundle`_ | Build an Android App Bundle file from your app |
144
-
| `build-bundle` | _see `flutter help build bundle`_ | Build the Flutter assets directory from your app |
145
-
| `build-ios` | _see `flutter help build ios`_ | Build an iOS application bundle (Mac OS X host only) |
146
-
| `buildIosframework` | _see `flutter help build ios-framework`_ | Produces a .framework directory for a Flutter module and its plugins for integration into existing, plain Xcode projects |
147
-
| `build-ipa` | _see `flutter help build ipa`_ | Build an iOS archive bundle (Mac OS X host only) |
148
-
| `clean` | _see `flutter help clean`_ | Delete the `build/` and `dart_tool/` directories |
149
-
| `drive` | _see `flutter help drive`_ | Run integration tests for the project on an attached device or emulator |
150
-
| `format` | _see `dart help format`_ | Format one or more Dart files |
151
-
| `gen-l10n` | _see `flutter help gen-l10n`_ | Generate localizations for the current project |
152
-
| `install` | _see `flutter help install`_ | Install a Flutter app on an attached device |
153
-
| `run` | _see `flutter help run`_ | Run your Flutter app on an attached device |
154
-
| `screenshot` | _see `flutter help screenshot`_ | Take a screenshot from a connected device |
155
-
| `symbolize` | _see `flutter help symbolize`_ | Symbolize a stack trace from an AOT-compiled Flutter app |
156
-
| `test` | _see `flutter help test`_ | Run Flutter unit tests for the current project |
| `analyze` | _see `flutter help analyze`_ | Analyze the project's Dart code |
139
+
| `assemble` | _see `flutter help assemble`_ | Assemble and build Flutter resources |
140
+
| `attach` | _see `flutter help attach`_ | Attach to a running app |
141
+
| `build-aar` | _see `flutter help build aar`_ | Build a repository containing an AAR and a POM file |
142
+
| `build-apk` | _see `flutter help build apk`_ | Build an Android APK file from your app |
143
+
| `build-appbundle` | _see `flutter help build appbundle`_ | Build an Android App Bundle file from your app |
144
+
| `build-bundle` | _see `flutter help build bundle`_ | Build the Flutter assets directory from your app |
145
+
| `build-ios` | _see `flutter help build ios`_ | Build an iOS application bundle (Mac OS X host only) |
146
+
| `buildIosframework` | _see `flutter help build ios-framework`_ | Produces a .framework directory for a Flutter module and its plugins for integration into existing, plain Xcode projects |
147
+
| `build-ipa` | _see `flutter help build ipa`_ | Build an iOS archive bundle (Mac OS X host only) |
148
+
| `clean` | _see `flutter help clean`_ | Delete the `build/` and `dart_tool/` directories |
149
+
| `drive` | _see `flutter help drive`_ | Run integration tests for the project on an attached device or emulator |
150
+
| `format` | _see `dart help format`_ | Format one or more Dart files |
151
+
| `gen-l10n` | _see `flutter help gen-l10n`_ | Generate localizations for the current project |
152
+
| `install` | _see `flutter help install`_ | Install a Flutter app on an attached device |
153
+
| `run` | _see `flutter help run`_ | Run your Flutter app on an attached device |
154
+
| `screenshot` | _see `flutter help screenshot`_ | Take a screenshot from a connected device |
155
+
| `symbolize` | _see `flutter help symbolize`_ | Symbolize a stack trace from an AOT-compiled Flutter app |
156
+
| `test` | _see `flutter help test`_ | Run Flutter unit tests for the current project |
157
+
| `pub-get` | _see `flutter help pub get`_ | Fetches and installs the dependencies listed in your `pubspec.yaml` file. |
158
+
| `pub-upgrade` | _see `flutter help pub upgrade`_ | Upgrades dependencies to the latest versions that match the constraints in `pubspec.yaml`. |
159
+
| `pub-downgrade` | _see `flutter help pub downgrade`_ | Downgrades dependencies to the earliest versions that match the constraints in `pubspec.yaml`. |
160
+
| `pub-outdated` | _see `flutter help pub outdated`_ | Lists outdated dependencies, showing current, upgradable, and latest versions. |
161
+
| `pub-add` | `--package=<pkg_name>` (required) _see `flutter help pub add`_ for the rest of options | Adds a new dependency to `pubspec.yaml` and fetches it. |
162
+
| `pub-remove` | `--package=<pkg_name>` (required) _see `flutter help pub remove`_ for the rest of options | Removes a dependency from `pubspec.yaml` and updates the package list. |
163
+
| `pub-run` | `--executable="<executable>"` (required) _see `flutter help pub run`_ for the rest of options | Runs an executable from one of your dependencies. |
164
+
| `pub-publish` | _see `flutter help pub publish`_ | Publishes your package to the Dart package repository (`pub.dev`). |
165
+
| `pub-deps` | _see `flutter help pub deps`_ | Displays a dependency graph of your package's dependencies. |
166
+
| `pub-version` | _see `flutter help pub version`_ | Shows the current version of the Dart SDK. |
157
167
158
168
<sup>1</sup> : _Actual executors in your `workspace.json` will depend on the type of `flutter` project (`template`), target `platforms` that you choose to generate._
159
169
160
170
Each executor is based on an original project-level `flutter` command. The name is just **kebab-cased** to match executors' naming conventions.
161
-
Besides, the arguments accepted by each executor, are the same as the original `flutter` command they are based upon, encapsulated
162
-
under a generic `--args='...'` option.
171
+
Besides, the addtional arguments accepted by each executor, are the same as the original `flutter` command they are based upon, and can be provided directly like in `--option=value`. Read this [guide](https://nx.dev/recipes/running-tasks/pass-args-to-commands#pass-args-when-running-the-command-in-the-terminal) for more about the syntax to pass arguments along.
163
172
164
173
For example:
165
174
166
175
```
167
176
$ flutter gen-l10n --header "/// my header"
177
+
$ flutter pub add builder_runner
178
+
$ flutter pub run build_runner build
168
179
169
-
becomes 👉🏾
180
+
become 👉🏾
170
181
171
-
$ nx gen-l10n your-flutterapp --args='--header="/// my header"'
172
-
```
182
+
$ nx gen-l10n your-flutterapp --header="/// my header"
0 commit comments