My colleague posted an interested article that addresses the disparity between an end-user of a typescript library and being a library author.
As the user of a library, not only do I hope for excellent documentation, but I also hope that the library author have designed an ergonomic API that provides clear and consistent typings when using TypeScript. What I acknowledge I lack is a clear understanding of the level of effort that is required. Designing and building a library is challenging, creating documentation takes time, and support TypeScript types is another burden that I place on library authors.
As the user of a library, not only do I hope for excellent documentation, but I also hope that the library author have designed an ergonomic API that provides clear and consistent typings when using TypeScript. What I acknowledge I lack is a clear understanding of the level of effort that is required. Designing and building a library is challenging, creating documentation takes time, and support TypeScript types is another burden that I place on library authors.
My goal of sharing this article is to add to the discussion of a recent article titled "TypeScript is terrible for library authors" (https://erock.prose.sh/typescript-terrible-for-library-devel...).