Bump tsd from v0.20.0 to v0.24.1

[watson]

This PR is to mainly bring main up to date with 7.17 so that it runs the same version of tsd (because we're bumping tsd in 7.17 in this PR: #144008). I guess I should have done the PR's in the other order and then just backported, but at the time I was only focused on fixing something in 7.17.

The tsd package is used by packages/elastic-safer-lodash-set and packages/kbn-utility-types. The only breaking changes according to the docs are that it now requires a newer Node.js version, which we adhere to. Since this is used as part of our test suite, I'd say that as long as the tests pass, we should be ok.

Blocked by

• Bump typescript 4.9 #144469

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: 339aa60
• Interpreting CI Failures

Failed CI Steps

• Checks

Metrics [docs]

Unknown metric groups

ESLint disabled in files

id	before	after	diff
osquery	1	2	+1

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	19	21	+2
fleet	57	63	+6
osquery	103	108	+5
securitySolution	439	443	+4
total			+17

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	20	22	+2
fleet	65	71	+6
osquery	104	110	+6
securitySolution	516	520	+4
total			+18

History

• 💔 Build #82745 failed 5e2f9ab

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @watson

[watson]

@dgieselaar After upgrading tsd it's saying that there's a TypeScript error in packages/kbn-utility-types/src/dot.ts which according to the CODEOWNERS file you "own". I've not been able to figure out how to fix what it's complaining about (see the "Checks" CI check or run node scripts/kbn run-in-packages test locally on this PR branch). Could I get you to have a look?

[dgieselaar]

@watson is this version of tsd compatible with the typescript version (4.6) we are using in the repo? It seems to use 4.8? https://github.com/SamVerschueren/tsd/releases/tag/v0.23.0

[watson]

@dgieselaar Do you think the version we use has to match the @tsd/typescript version that tsd depends on? I can't find anything about it in their documentation 🤷

[dgieselaar]

@watson I would think so yeah, otherwise we get different errors from CLI type check/IDE on one side vs TS tests, which I think is what we are seeing here.

[watson]

Ok 👍 I've marked this PR as blocked by #144469