(poll) Choose ONE (1) invocation for pnpm dlx/pnpx/etc

[AMDphreak]

pnpm dlx has too many aliases. This is confusing and annoying to have to memorize alternate options for your CLI app on top of all the other tools we have to memorize. Minimize the surface area of your command line. It is not helpful to have all of these aliases. It is confusing and that is all. Standardize onto ONE (1) invocation for a single action. Many-to-1 mapping is not appropriate in a terminal command's available syntax.

https://stackoverflow.com/questions/73427676/what-is-difference-between-pnpm-create-pnpx-dlx

pnpm exec is a subset of pnpm dlx. It should not be its own command but instead a flag/option of pnpx.

[zkochan]

pnpm exec isn't a subset of pnpm dlx. pnpm exec runs a locally installed binary and doesn't install anything. pnpm dlx installs a binary in a temporary location and runs it.

[JNEWSP]

I’d personally standardize on pnpm dlx as the single primary spelling, and keep the others as deprecated aliases for a while for backwards compatibility.

Reasons:

• dlx already has the “one‑off command / global tool” mental model in the pnpm ecosystem, while exec is more associated with “run in the current project context”. Overloading exec for both could be confusing.
• Keeping pnpm dlx avoids name collision / confusion with npm’s npx, but is still close enough in spirit that users can transfer their mental model from npx → dlx.
• Having one official form makes docs, examples, and teaching simpler; aliases can still exist but be documented as legacy.