I am interested in use cases such as<p>- server-side libraries ex: sentry serverside clients<p>- front-end libraries ex: react-query<p>I am interested in aspects like API design, architectural decisions, dev tooling and etc.
A famous guide to evaluate your APIs:<p>- <a href="https://ozlabs.org/~rusty/index.cgi/tech/2008-03-30.html" rel="nofollow">https://ozlabs.org/~rusty/index.cgi/tech/2008-03-30.html</a><p>- <a href="https://ozlabs.org/~rusty/index.cgi/tech/2008-04-01.html" rel="nofollow">https://ozlabs.org/~rusty/index.cgi/tech/2008-04-01.html</a>
Josh Bloch did a good google tech talk on general aspects of API design.<p><a href="https://www.youtube.com/watch?v=heh4OeB9A-c" rel="nofollow">https://www.youtube.com/watch?v=heh4OeB9A-c</a>
One thing I can say which is probably a low hanging fruit. Error handling. Return errors in such a way that the application using the library can actually do something with it.
For documentation, this site has a good framework for organizing library docs: <a href="https://diataxis.fr/" rel="nofollow">https://diataxis.fr/</a>