ComposioHQ/composio · error · Error
No classes found in TypeDoc output
Error message
No classes found in TypeDoc output
What it means
Internal docs-generation script error: TypeDoc ran but its project reflection has no children, meaning it parsed no exported classes. This indicates an empty/broken parse of the source, not a problem with the SDK runtime.
Source
Thrown at ts/packages/core/scripts/generate-docs.ts:1176
async function main() {
console.log('Starting TypeScript SDK documentation generation...\n');
console.log(`Package dir: ${PACKAGE_DIR}`);
console.log(`Output dir: ${OUTPUT_DIR}\n`);
// Clean output directory
try {
await rm(OUTPUT_DIR, { recursive: true, force: true });
} catch {
// Directory doesn't exist, that's fine
}
await mkdir(OUTPUT_DIR, { recursive: true });
// Run TypeDoc
const project = await runTypeDoc();
if (!project.children) {
throw new Error('No classes found in TypeDoc output');
}
// Auto-discover classes to document (excludes internal classes)
const classesToDocument = discoverClassesToDocument(project);
console.log(
` Found ${classesToDocument.length} classes to document: ${classesToDocument.join(', ')}`
);
// Find and document each class
const documented: { name: string; description: string }[] = [];
for (const className of classesToDocument) {
const reflection = findClass(project, className);
if (!reflection) {
console.warn(` Warning: ${className} not found in TypeDoc output`);
continue;
}View on GitHub (pinned to 64b1b85502)
Solutions
- Verify the TypeDoc entryPointStrategy/entryPoints config still points at real source files
- Build the package first (pnpm build:packages) so generated/compiled surfaces exist
- Check the pinned TypeDoc version hasn't drifted; re-pin if a major bump changed output
- Debug runTypeDoc() output to confirm the project reflection is populated
Defensive patterns
Strategy: try-catch
Validate before calling
const project = await runTypeDoc();
if (!project.children?.length) failFast('entry points misconfigured'); Try / catch
try { await main(); } catch (e) { if (e.message === 'No classes found in TypeDoc output') { console.error('check TypeDoc entryPoints'); process.exit(1); } } Prevention
- Build packages before running docs generation
- Pin the TypeDoc version
When it happens
Trigger: Running scripts/generate-docs.ts when TypeDoc entry points are misconfigured, the build/entry files are missing, or TypeDoc version changes yield a different project shape.
Common situations: CI docs job after a refactor moved entry points; TypeDoc major-version bump changing output structure; running the script before building the package.
Related errors
AI-assisted analysis of ComposioHQ/composio@64b1b85502 (2026-08-28).
Data as JSON: /api/errors/d4ee0d77a8c8ac24.
Report an issue: GitHub.