Currently, a basic api-extractor.json looks something like:
{
"$schema": "https://dev.office.com/json-schemas/api-extractor/api-extractor.schema.json",
"compiler" : {
"configType": "tsconfig",
"rootFolder": "."
},
"project": {
"entryPointSourceFile": "lib/index.d.ts"
}
}
which works great for repos that only contain one src root. However, it'd be great if it were possible to supply multiple projects/roots/entry points to better support monorepos. Perhaps you get this for free with Rush as your monorepo solution (?) or the suggested approach would be to roll extraction/doc generation at a per package level via their respective gulp task (or similar), but it'd be quite handy to be able to accomplish it from the CLI as well.
Currently, a basic
api-extractor.jsonlooks something like:which works great for repos that only contain one src root. However, it'd be great if it were possible to supply multiple projects/roots/entry points to better support monorepos. Perhaps you get this for free with Rush as your monorepo solution (?) or the suggested approach would be to roll extraction/doc generation at a per package level via their respective gulp task (or similar), but it'd be quite handy to be able to accomplish it from the CLI as well.