If you think #ai is good at writing #documentation (comments, #JSDocs, commit messages etc.), you misunderstood the whole concept of documentation.

@thilo I've not used external definitions much personally, except when I need to import a type from a library. @enhance_dev does a great job of using #JSDoc for types in their docs. @see: https://enhance.dev/docs/learn/practices/types

#jsdocs #typescript

@thudfactor Typescript is a good linter, but nobody should ever feel bad about just telling it to ignore and getting back to work. This is why I use #JSDocs instead of #Typescript syntax

#webdev

@paulhmason +1 never having a problem with TypeErrors.

But I think types are actually valuable for

A) refactoring (errors can show you all the places your changes have effect)
B) interpreting other people's code (types can provide documentation, not just type)

I use #JSDocs with #VSCode.

I avoid using #Typescript syntax though. Linting errors should never prevent you from running code.

TIL you can import #TypeScript types into #JSDocs using @typedef:

/**
* @typedef { import("../setup").Tool } Tool
*/