Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don’t have a strong opinion here either – ignoring yarn.lock to avoid lockfile conflicts when using Yarn makes sense if we want true multi–package-manager support.

We could also explore enforcing a single manager via devEngines as @bjohansebas said, but that’d be a more restrictive approach.

Given that this change is harmless for npm/pnpm users and just skips committing the Yarn lockfile, I’m happy to approve.