fix: local execute for yarn v1 and 2+ compatibility

[vinnymac]

For when we publish npmx-connector to npm enable package manager preferences, this will make the command for yarn package manager become npx npmx-connector.

It also means npx will be used anywhere yarn local execution is accessed. Which I think is fine. Interestingly, "execute remote" is currently set to yarn dlx still, which is only supported by Yarn 2+.

I might get shade for saying it, but we may want to consider only supporting Yarn 2+ and dropping Yarn 1 users given how old and outdated it is and so many better alternatives around. Just my two cents. As-is the current UI doesn't really support v1 of yarn, since dlx is not an option.

Closes #515

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Jan 31, 2026 7:53pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
npmx-lunaria	Ignored		Jan 31, 2026 7:53pm
docs.npmx.dev	Skipped		Jan 31, 2026 7:53pm

[wojtekmaj]

Your changes without proper investigation may look like an error at first glance. I'd sprinkle it with some inline comments if I were you.

[serhalp]

I think it's common enough to treat yarn v1 and yarn "berry" v2+ as effectively two different package managers. We could just have them be separate options. Or not support v1...

and technically for yarn v1 we could use yarn global add npmx-connector && npmx-connector

[wojtekmaj]

I mean yeah but for the sake of what? It is important for devs to have install commands crafted specially for their package manager, but for one-time command no one could possibly care. I'd just scrap the whole thing and just hardcode this to npx command for every package manager :D

[danielroe]

npx would honestly be fine for me for this one.