mirror of
https://github.com/flutter/packages.git
synced 2025-06-19 13:38:53 +08:00
eed9b68284
Now that the repo tooling is always run from source, not via `pub global`, we no longer need to infer the repo location from the current directory. Instead, hard-code knowledge of where the repository root is. This makes it much easier to run the tooling, since it's common to be in a package directory rather than the repo root. To make it even easier to run from within a package, this also adds a `--current-package` as an alternative to `--packages`. This makes it possible to, e.g., write local wrapper scripts that run a specific set of commands on whatever the current package happens to be (such as a generic version of the script discussed in https://github.com/flutter/packages/pull/4129). As related cleanup, makes the tool non-publishable (we haven't been publishing it since the repo merge, but I never made it unpublishable; this is important now that it would not work if published) and remove the LICENSE and CHANGELOG since it's no longer a stand-alone package. Fixes https://github.com/flutter/flutter/issues/128231 Fixes https://github.com/flutter/flutter/issues/128232
35 lines
725 B
YAML
35 lines
725 B
YAML
name: flutter_plugin_tools
|
|
description: Productivity and CI utils for flutter/packages
|
|
repository: https://github.com/flutter/packages/tree/main/script/tool
|
|
version: 1.0.0
|
|
publish_to: none
|
|
|
|
dependencies:
|
|
args: ^2.1.0
|
|
async: ^2.6.1
|
|
collection: ^1.15.0
|
|
colorize: ^3.0.0
|
|
file: ^6.1.0
|
|
# Pin git to 2.0.x until dart >=2.18 is legacy
|
|
git: '>=2.0.0 <2.1.0'
|
|
http: '>=0.13.3 <2.0.0'
|
|
http_multi_server: ^3.0.1
|
|
meta: ^1.3.0
|
|
path: ^1.8.0
|
|
platform: ^3.0.0
|
|
pub_semver: ^2.0.0
|
|
pubspec_parse: ^1.0.0
|
|
quiver: ^3.0.1
|
|
test: ^1.17.3
|
|
uuid: ^3.0.4
|
|
yaml: ^3.1.0
|
|
yaml_edit: ^2.0.2
|
|
|
|
dev_dependencies:
|
|
build_runner: ^2.0.3
|
|
matcher: ^0.12.10
|
|
mockito: '>=5.3.2 <=5.4.0'
|
|
|
|
environment:
|
|
sdk: '>=2.14.0 <4.0.0'
|