Fix: eslint warning in code example from the documentation: void is not valid as a constituent in a union type

[Josef-Friedrich]

eslint@typescript-eslint/no-invalid-void-type

Description

When I copy the example from the documentation into my project, these warnings appear:

void is not valid as a constituent in a union type eslint@typescript-eslint/no-invalid-void-type

Using undefined instead of void will fix this problem

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for fastidious-cascaron-4ded94 ready!

Name	Link
🔨 Latest commit	2238c71
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/65ef79298a5dac0008979443
😎 Deploy Preview	https://deploy-preview-5371--fastidious-cascaron-4ded94.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sheremet-va]

1. This just changed it in the documentation, shouldn't it be also changed in the source code?
2. Isn't there another eslint rule that forces undefined to be returned if it's specified as a return type?