chore: update dev dependencies

[targos]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.66%. Comparing base (525db22) to head (c0e635e).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #327   +/-   ##
=======================================
  Coverage   96.65%   96.66%           
=======================================
  Files         200      200           
  Lines        5923     5935   +12     
  Branches     1307     1307           
=======================================
+ Hits         5725     5737   +12     
  Misses        198      198           

☔ 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.

[targos]

@mljs/collaborators I take the opportunity to show you this. The last release of the ESLint config adds a rule about sort(), similar to reverse() that we already have.
Note that the error message tells to use toSorted() and toReversed(), which sometimes is the right thing to do (for example to not modify the input), but there is another option: it is allowed to call .sort() and .reverse() like that as a statement.

[stropitek]

So the error only shows up when the return value of sort or reverse are assigned to something?

[targos]

Not exactly. The error shows up when the call is part of an expression. So another case for example is when you pass the return value directly to a function call: myFunction(arr.sort())

[stropitek]

ok that makes a lot of sense