Proposal: Change priority of script resolution

The debug logs we introduced in v6 helps to identify the problem but there have been numerous issues opened because of the way findBin works currently. Specifically, many users inadvertently define a script in the package.json which conflicts with the installed linter like prettier. However, I think having the option to run arbitrary scripts by defining them in the package.json is a useful feature and we shouldn’t drop it. Instead, how about changing the priority such that we look for installed binaries first and check the package scripts only if a binary could not be resolved? This would be a breaking change though.

[okonet]

I would vote against it since I believe this will introduce not less but probably even more confusion. I actually think that dropping this might be a good idea. Too much magic 🔮 😃

Another benefit is that it will allow people choose which runner to use by writing yarn task:name or npm run task:name which isn’t the case ATM.

Migration path could be a bit of pain but if we can make a nice validation message about it, it would be an easy one I think.

Thoughts?

[okonet]

Was closed in v7