Add wrangler2 as an alias

[TehShrike]

So that when wrangler2 is installed along @cloudflare/wrangler, they can each be referenced in npm run scripts.

See cloudflare/wrangler-legacy#2139

[TehShrike]

My current workaround is to publish a fork https://www.npmjs.com/package/@tehshrike/wrangler2

[GregBrimble]

Pretty sure can reference wrangler v1 with npx @cloudflare/wrangler, so you should be able to avoid this conflict already.

[threepointone]

This PR seems unnecessary. You can install wrangler locally to a project and refer to it via npm scripts, or use npx.

[threepointone]

As mentioned

[TehShrike]

Pretty sure can reference wrangler v1 with npx @cloudflare/wrangler, so you should be able to avoid this conflict already.

Nope, I tried that – npx looks up @cloudflare/wrangler, checks to see what its bin script name is, looks in node_modules/.bin, sees that wrangler exists there, and calls it, even if it points to the script in node_modules/wrangler.

This PR seems unnecessary. You can install wrangler locally to a project and refer to it via npm scripts, or use npx.

There is currently no way to install both wrangler and @cloudflare/wrangler and reliably execute one or the other via npm run scripts.

I was not using any global scripts, I was only using versions of wrangler that were direct dependencies of my project.

[threepointone]

Noted, thanks for the investigation. Lemme think about this, but I'm leaning towards merging this atm.