Pete Gonzalez

A little background about API Extractor's design philosophy: > if we were to change it to: > > ```ts > interface Response { > user: User > } > >...

> One basic proposal is to add a new `"includeForgottenExports": boolean` setting to the `api-extractor.json` file. If false (default value), API Extractor works just as it does today. If true,...

A couple other thoughts: ### Declaration references If unexported API items are documented, then the `{@link}` tag needs to be able to reference them. The old TSDoc [declaration reference](https://tsdoc.org/pages/spec/overview/) syntax...

> However, is there a situation where we'd want an unexported API to be included in the API report but not the API doc model (or vice versa)? No sure...

@dmichon-msft @D4N14L Do you cache files under the `.heft/` folder?

@elliot-nelson where would the fix go? In Heft? In Rush? In the config files for this monorepo?

This is a good proposal. @postspectacular are you able to help implement it?

FYI there's some general instructions in the [Contributing](https://api-extractor.com/pages/contributing/building/) doc. If you don't have time, let me know. I might be able to help, although I've been pretty busy with https://github.com/microsoft/tsdoc/pull/196...

We need a volunteer to implement it

Before using PNPM `>=6.32.12`, we ideally should first make the Rush PR that sets `ignore-compatibility-db=true`. (See https://github.com/pnpm/pnpm/issues/5132 for details)