4 ms·
I agree on ignoring libraries without definitions. Having to write the definitions myself usually isn't a huge pain, but it's a big red flag showing that it's
by horsawlarway 6y ago
I agree on ignoring libraries without definitions.
Having to write the definitions myself usually isn't a huge pain, but it's a big red flag showing that it's probably abandoned, and there's no community support around it anymore (or possibly ever).
- a_humean 6y agoYep, these days its basically a proxy for the kinds of smells you look out for when picking a library.
- WorldMaker 6y agoIn those cases I will sometimes try to post an offer to write their definitions (or the build step to generate definitions from slightly modified existing JSDoc comments in even more rare cases) and PR them to the project if they like. How a project responds (or doesn't) to that Issue often tells you so much about current maintenance habits.