Nicky McCurdy

That's fair. Would a draft PR to test changing the build, or would you rather wait until the types are more ready?

How about a Creative Commons license? Those are usually pretty good for open documentation content, and there are flexible variants like non-commercial, share-alike, and public domain.

It would be nice to migrate the recipes to hooks as well (I updated the testing one in #3876). Would a separate issue be better or would you like to...

That link you quoted is broken but the link on the page seems to be working now. The broken version might be cached for you. Have you tried reloading?

You mean like a git [submodule](https://git-scm.com/book/en/v2/Git-Tools-Submodules) or [subtree](https://www.atlassian.com/git/tutorials/git-subtree)?

I don't think you can symlink across repositories, unless you require users always clone both repositories in the same place relatively, but they that would probably break on GitHub. GitHub...

Would this still be compatible with old types when not giving the state?

That could be a branch. FWIW [Testing Library](https://github.com/testing-library) has [one site repo](https://github.com/testing-library/testing-library-docs) and it seems to be working well so far.

`@jest/types` is not a replacement for `@types/jest`. `@jest/types` exports some TypeScript types for internal Jest packages so external packages can import them, but it does not provide global types or...

Unfortunately if we use the same API and try to hide the async Promises from non-Puppeteer users, we run into issues with `@typescript-eslint/require-await` which would require `await` even when not...