lang-typescript

To detect public APIs across TypeScript and JavaScript source files, analyze exports, interfaces, types, enums, and React components. This process maps public symbols to their origin sources, including barrel files, producing a coherent API documentation plan.

Resolving barrel file re-exports to their actual source symbols requires tracing exports back to their original definitions in .ts or .tsx files. This ensures accurate documentation mapping and prevents documenting the barrel aggregator itself.

Yes, you can enforce JSDoc and TSDoc formatting standards for React component props and return types. The enforcement applies to parameters, returns, and prop documentation requirements across TS/JS projects of varying sizes.

The best way to plan API documentation for a TypeScript project is to perform API surface analysis by detecting public functions and classes. This aligns documentation with source definitions and enforces JSDoc/TSDoc standards for auditing workflows.

Yes, this API detection approach works with both JavaScript and TypeScript projects. It implements detection across source files including .ts, .tsx, .js, and .jsx, ensuring JSDoc/TSDoc formatting and accurate symbol mapping.