[puppy] Introduce a package for misc Dart CLI tools

[kevmoo]

First tool: for_all_package_dirs to recursively run a command in every
directory that contains pubspec.yaml

[kevmoo]

Will rebase once #334 lands!

[github-actions]

PR Health

Breaking changes ✔️

Package	Change	Current Version	New Version	Needed Version	Looking good?

Changelog Entry ✔️

Package	Changed Files

Changes to files need to be accounted for in their respective changelogs.

Coverage ✔️

File	Coverage

This check for test coverage is informational (issues shown here will not fail the PR).

API leaks ✔️

The following packages contain symbols visible in the public API, but not exported by the library. Export these symbols or remove them from your publicly visible API.

Package	Leaked API symbols

License Headers ✔️

// Copyright (c) 2025, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

Files
no missing headers

All source files should start with a license header.

[kevmoo]

CC @jakemac53 RE convo in chat

[devoncarew]

Some high level comments:

• we may want a single entry-point here - to use puppy <command> and the package:args CommandRunner stuff
• we may also want to leverage the pkgs convention - to not traverse into subdirectories arbitrarily
• instead of an arbitrary 'run anything' command, should we instead have specific pub get / ... other commands?
• if we do have a 'run anything' command, we'd probably want a shorter name than for_all_package_dirs; perhaps map (for map-reduce)?

[kevmoo]

Some high level comments:

• we may want a single entry-point here - to use puppy <command> and the package:args CommandRunner stuff

Maybe? I lean towards specific top-level CLIs. They autocomplete where subcommands don't. Unless you have auto-complete magic installed.

• we may also want to leverage the pkgs convention - to not traverse into subdirectories arbitrarily

I have cases where the package is NOT set up that way. I guess we could add a depth option or similar?

• instead of an arbitrary 'run anything' command, should we instead have specific pub get / ... other commands?

Disagree. It's super nice to be able to run anything. Like dart run build_runner or similar

• if we do have a 'run anything' command, we'd probably want a shorter name than for_all_package_dirs; perhaps map (for map-reduce)?

Agreed if we go w/ the one top-level thingy

[devoncarew]

• we may want a single entry-point here - to use puppy <command> and the package:args CommandRunner stuff

Maybe? I lean towards specific top-level CLIs. They autocomplete where subcommands don't. Unless you have auto-complete magic installed.

I'd prefer a single entry-point - I think it scales better as we get more commands - but it's not a blocker for me.

• we may also want to leverage the pkgs convention - to not traverse into subdirectories arbitrarily

I have cases where the package is NOT set up that way. I guess we could add a depth option or similar?

Can we just not support those repos? Or encourage the //pkgs/ convention?

I'm just hesitant of arbitrary recursion, and supporting nesting of nesting. Perhaps we stop looking after we've hit a pubspec dir? Or do that by default and have a flag to just keep going.

• instead of an arbitrary 'run anything' command, should we instead have specific pub get / ... other commands?

Disagree. It's super nice to be able to run anything. Like dart run build_runner or similar

OK, makes sense.

• if we do have a 'run anything' command, we'd probably want a shorter name than for_all_package_dirs; perhaps map (for map-reduce)?

Agreed if we go w/ the one top-level thingy

I like map :) But that's bikeshedding.

[jakemac53]

I'm just hesitant of arbitrary recursion, and supporting nesting of nesting. Perhaps we stop looking after we've hit a pubspec dir? Or do that by default and have a flag to just keep going.

We should probably at least support example dirs, although if this is just for our own tooling then it might not really matter, because we don't really use that pattern outside of flutter.

[kevmoo]

How about default to no recursing deeper than the first discovered pubspec – unless you opt in

In my experience, it rarely causes issues...just (often) failures

[devoncarew]

Is there a way to pipe through command aliases here? If we wanted to instead support puppy run?

[kevmoo]

Oh crap! I forgot! Just submit a PR to change that now.