This is marked as draft because there are still many errors; the majority of them, afaict, are due to webpack's type definitions relying on the presence of @types/node. I'm not sure what the proper way to mark the affected packages as requiring @types/node is, given that it's a dependency requirement, and not needed in the types themselves.

Once I know the proper way to add @types/node, I can do that in bulk and fix the remainder of the errors.

I noticed the existence of #49755, but that doesn't nearly update all the relevant packages, so I though it would be useful to open a PR with the relevant packages updated in bulk.

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change.
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm test <package to test>.

Select one of these and delete the others:

If removing a declaration:

• If a package was never on Definitely Typed, you don't need to do anything. (If you wrote a package and provided types, you don't need to register it with us.)
• Delete the package's directory.
• Add it to notNeededPackages.json.