How to avoid a potential bug with JSDoc + @typedef
With no build-step in sight, it can be tempting to put more and more type information into comments.
With no build-step in sight, it can be tempting to put more and more type information into comments.
After a deep dive, I now consider both to be dangerous.
A problem that even the strictest Typescript/ESLint settings cannot help with.
Showing how you can re-use the same name for types and values with Zod. Includes sample in Typescript + JSDoc
As a serial stop/start blogger I've written in countless places in the past. The following links represent the ones I stayed around long enough for
Previous articles written on Dev.to
dev.to/shakyshane
Previous articles written on Medium
medium.com/@shakyShane