#16803 Ability to `run` (or `package`?) an `experimental_shell_command` Issue created by danxmoran Is your feature request related to a problem? Please describe. Currently (as far as I can tell) the only way to test that an

experimental_shell_command

works properly is to wire it up to a downstream target (the docs mention

docker_image

) and have the build process for that target inspect the shell outputs. There's no way to run the command in isolation to manually check its outputs in isolation, which is a drag when you're prototyping / debugging. Describe the solution you'd like The ability to

./pants run

an

experimental_shell_command

target and have the outputs appear under

dist/

. If it's weird for a

run

command to produce

dist/

output, I could also see an argument for

package

on these targets. Describe alternatives you've considered The work-around is to add a downstream target and use that target to inspect the shell command's outputs. Doable, but an unfortunate hoop to jump through. Additional context The related

experimental_run_shell_command

is

run

-able, but you can't have any other targets depend on its output. pantsbuild/pants

#16803 Ability to `run` (or `package`?) an `experimental_shell_command` Issue closed as completed by danxmoran pantsbuild/pants