chore(deps): update peerdependency neverthrow to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
neverthrow	^5.1.0 -> ^6.2.2

---

Release Notes

supermacro/neverthrow (neverthrow)

v6.2.2: Performance improvements 🏎️ 💨

Compare Source

This patch ships https://github.com/supermacro/neverthrow/pull/538 which makes the combine APIs significantly faster. Now running the combine apis on large lists is significantly faster.

Thank you @​flowreaction for the PR 👏

v6.2.1: Fix empty dist folder

Compare Source

Fixes https://github.com/supermacro/neverthrow/issues/532

v6.2.0: New ResultAsunc.fromThrowable

Compare Source

Addresses https://github.com/supermacro/neverthrow/issues/488 & implements the .fromThrowable method on ResultAsync.

Thanks to @​ehaynes99 for implementing this 🚀

---

👉 Reminder; I'm looking for a maintainer to help out:

https://github.com/supermacro/neverthrow/issues/531

v6.1.0: Emulation of Rusts ? Result operator (implicit return for errors)

Compare Source

neverthrow now can support implicit return whenever there is an Err instance inside of a generator.

Context: https://github.com/supermacro/neverthrow/pull/448

Thank you to @​tsuburin for the contribution 🚀

---

Additionally, the previous functionality around increasing the tuple size supported by neverthrow is now live and out of beta. Context: https://github.com/supermacro/neverthrow/releases/tag/v6.0.1-0

v6.0.0: Resolve accidental breaking change with type inference on array types

Compare Source

The combine* family of functions (both sync and async) broke any codebase that called these functions on arrays of varying lengths when the previous release was shipped:

https://github.com/supermacro/neverthrow/releases/tag/v5.1.0

The following fix was implemented to address this issue and ensure that arrays (not just tuples) work with the combine* family of functions.

https://github.com/supermacro/neverthrow/pull/435

Why is this shipped as a MAJOR version change?

Because we are now explicitly depending on TypeScript's variadic tuple types feature, which came out in v4 of TypeScript:

https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-0.html#variadic-tuple-types

Acknowledgements

Thank you to @​ghost91- for implementing the fix 🙏

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.