fix: remove pnpm from engines

[friederbluemle]

Checks

• I have read the contributing guidelines.

Changes

Remove pnpm field from engines in package.json

Context

During dependency installation in my project using Yarn, I noticed the following message:

warning [email protected]: The engine "pnpm" appears to be invalid.

The pnpm entry in engines was introduced in #966, which migrated from npm to pnpm. The same PR also correctly sets packageManager to pnpm - That's the important field used when developing eslint-plugin-testing-library itself.

There is no reason to require consumers of eslint-plugin-testing-library to use pnpm (or any specific package manager). Therefore, the best solution is to simply remove the entry from engines altogether.

[Belco90]

@friederbluemle Good point! Thanks 🙏

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.51%. Comparing base (67ade2e) to head (3e04994).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1117   +/-   ##
=======================================
  Coverage   96.51%   96.51%           
=======================================
  Files          51       51           
  Lines        2872     2873    +1     
  Branches     1179     1175    -4     
=======================================
+ Hits         2772     2773    +1     
  Misses        100      100           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

🎉 This PR is included in version 7.13.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀