Nicky McCurdy

Oh good point, I didn't try that. I ended up doing the rest manually, fortunately it only skipped my archived cards. Thanks for the advice though. Is this using an...

My problems are resolved anyway since I finished my only import. Want to leave this open or close it and have people use `--statedir` as a workaround?

You can give it `--dryrun true` as a workaround, but I agree.

I just want to have one command that upgrades Yarn to the latest 1 and everything else to the latest major. It was removed in #351 with no documentation.

If I install Yarn modern globally, will Yarn classic still be used if I don't have `packageManager` in a local `package.json`? I'm fine with global usage, I just don't want...

> If I install Yarn modern globally, will Yarn classic still be used if I don't have `packageManager` in a local `package.json`? I'm fine with global usage, I just don't...

Technically, adding any `engines` here is a breaking change, since it could prevent installations from users on older Node versions. I think we should revert commit that unless we're ready...

We could publish this as a minor, and worst case if there are back compatibility issues (probably unlikely), we could revert it.

It seems like the CI config is broken for any PR currently.

Should we archive this repository in favor of https://codesandbox.io/s/react-testing-library-help-uztri? It's a fork of your sandbox, which I believe was forked from this repository.