#Twoslash

Every #TypeScript library I maintain uses Twoslash. I still haven't regretted it, even when Fedify's docs take nearly ten minutes to build. That wait is annoying. I keep paying it.

For a TypeScript library, the type signature often does most of the explaining. I used to write sentences describing what a function returns. Now I'd rather let #Twoslash show the compiler's answer inline. That removes one common way my docs used to go stale.

Every #TypeScript library I maintain uses Twoslash. I still haven't regretted it, even when Fedify's docs take nearly ten minutes to build. That wait is annoying. I keep paying it.

For a TypeScript library, the type signature often does most of the explaining. I used to write sentences describing what a function returns. Now I'd rather let #Twoslash show the compiler's answer inline. That removes one common way my docs used to go stale.

Every #TypeScript library I maintain uses Twoslash. I still haven't regretted it, even when Fedify's docs take nearly ten minutes to build. That wait is annoying. I keep paying it.

For a TypeScript library, the type signature often does most of the explaining. I used to write sentences describing what a function returns. Now I'd rather let #Twoslash show the compiler's answer inline. That removes one common way my docs used to go stale.

Every #TypeScript library I maintain uses Twoslash. I still haven't regretted it, even when Fedify's docs take nearly ten minutes to build. That wait is annoying. I keep paying it.

For a TypeScript library, the type signature often does most of the explaining. I used to write sentences describing what a function returns. Now I'd rather let #Twoslash show the compiler's answer inline. That removes one common way my docs used to go stale.

Every #TypeScript library I maintain uses Twoslash. I still haven't regretted it, even when Fedify's docs take nearly ten minutes to build. That wait is annoying. I keep paying it.

For a TypeScript library, the type signature often does most of the explaining. I used to write sentences describing what a function returns. Now I'd rather let #Twoslash show the compiler's answer inline. That removes one common way my docs used to go stale.

#Twoslash is great for improving the quality of the docs, but the downside is that it slows down the build time tremendously. 😩

I'm applying #Twoslash to the #Fedify docs. It works like magic! When I'm done, the Fedify docs will be even easier to read the example code than they are now.