Why does the package still ship a wrangler2 binary alias?

[toreis-up]

I noticed that the wrangler package still includes a wrangler2 bin entry that points to the same executable despite wrangler-legacy is already deprecated 1.5 yrs ago...

workers-sdk/packages/wrangler/package.json

Lines 40 to 43 in ffc30d3

	"bin": {
	"wrangler": "./bin/wrangler.js",
	"wrangler2": "./bin/wrangler.js"
	},

Context

• PR: Add wrangler2 as an alias in Add wrangler2 as an alias #40
• The older wrangler project (wrangler-legacy) was deprecated roughly two years ago. Given that history, the current wrangler2 alias appears to be a compatibility/transition artifact rather than a separate maintained binary.

Could it be removed or does it need to be kept for backward compatibility?

[MattieTK]

Good spot. During the migration between the first and second versions of wrangler, we added this to aid in migration. There's really no need for it anymore though and we will remove it in a future version.

[toreis-up]

Thank you for your reply.

If it's okay with you, I can create a delete PR. What do you think?