poor UX when resetting lockfiles

[aep-sunlife]

Hi,

yarn overcomplicates the process of resetting all lockfiles, junkfiles, etc.

• When I remove .yarn, .pnp.*, and yarn.lock, then the next yarn install fails. This command should understand how to regenerate everything again, like npm install, based on an existing package.json file. Instead, it bails with an assortment of confusing options.
• yarn init always forcibly overwrites existing package.json files. Instead, it should first check whether the file exists. Only overwrite if the file definitely does not exist.

So the workaround workflow involves manually backing up my package.json file, running yarn init, and replacing the stub package.json file from my backup. That's risky, manual, and unintuitive. We're moving backwards from npm capabilities.