ts-check-jsdoc-experiment

To enable TypeScript type checking in plain JavaScript, add // @ts-check at the top of your JS file and use JSDoc annotations to define types. This allows editors and build tools to catch type errors without converting your codebase to TypeScript.

Gradual migration to TypeScript is best achieved by using // @ts-check and JSDoc type annotations in existing JavaScript files. This approach incrementally introduces static typing to preserve your current code structure while catching type errors early during the transition.

Yes, you can use JSDoc to describe types, interfaces, and typedefs across JavaScript modules. By enabling // @ts-check, the TypeScript checker interprets these JSDoc annotations to provide static type validation directly within your plain JS files.

The // @ts-check directive works with existing JavaScript build pipelines and editors by enabling the TypeScript checker on plain JS files. It allows you to validate JSDoc type definitions during builds without requiring a full TypeScript compilation setup.

You should avoid relying solely on JSDoc type annotations when your project requires complex TypeScript features beyond static typing, such as advanced generics or enums. This approach is designed for gradual migration and learning environments, not as a complete replacement for native TypeScript syntax.