Nicky McCurdy

> This occurs in Wezterm too, so I don't think it's just a VSCode issue unless they both use Harfbuzz. It's likely they both are, as Wezterm uses it by...

Thanks for clarifying, I had a feeling this would be the case but wanted to confirm.

This appears to be a [VSCode bug](https://github.com/microsoft/vscode/issues/198517). However, the documentation should still be consistent.

While I'd normally recommend custom hooks, I see your point about difficulty refactoring. We're already considering a [`reactStrictMode` option](https://github.com/testing-library/react-testing-library/issues/338) for DTL's `configure` API, so I think this would be worth...

Agreed, that would also give us time to update DTL or our supported Node versions before a major release (see https://github.com/testing-library/dom-testing-library/pull/1255).

> But I would also not force the Node.js 18 bump unless it is necessary or enables some new feature. It's necessary for security. [Node 16 is intentionally ending support...

@kentcdodds Sounds like a good idea! I suggest we continue working on the other breaking changes for RTL (porting testing-library/dom-testing-library#1255 and then updating the dependency on DTL) in `alpha` (we're...

I'm in favor of using optional peer dependencies too, as I've had module not found errors using Testing Library packages with strict package managers (pnpm, npm without the default `install-strategy`,...

Actually this might be a duplicate of #1103. @eps1lon what do you think?

Supporting Vitest timers should be as easy as calling `vi` instead of `jest`, and historically we've had messier code supporting differences in DOM implementations, so I think it's worth trying....