Pete Gonzalez

If API Extractor produces the rolled up .d.ts file, then API Extractor would need to produce the corresponding .d.ts.map file. (The **combine-source-map** or **sorcery** tools can be used to repackage...

Interesting. Can you clarify why would it be useful to have a .d.ts.map for API Extractor's .d.ts rollup? What would you use that declaration map for?

I see, so when a consumer imports your published NPM package, the compiler will use the .d.ts rollup. But when the developer presses F12 in VS Code ("go to definition"),...

If API Extractor generates a .d.ts.map for the rollup, should the mapping should try to point to the original .ts file, NOT to the intermediary .d.ts file that the .d.ts...

Sounds like a plan. If someone wants to work on this, the existing code that uses .d.ts.map file to remap error messages is in [SourceMapper.ts](https://github.com/microsoft/rushstack/blob/aac158f7d662b76fd2b913400bc0f8e252c2c647/apps/api-extractor/src/collector/SourceMapper.ts). This new feature will probably...

I have not had time to work on this yet, or even to think about what's involved and what's the best approach. I do agree it's an important feature. I'll...

One of the main benefits of a monorepo is the "you broke it, you fix it" property: *A PR cannot merge unless it successfully passes the tests for all downstream...

> I haven't looked at the source yet, but it seems that at the point that Rush detects changes, instead of running `getFiles(exec('git diff ...'))` (or similar pseudo code) it...

> Currently we have a lot of git repos and we want to migrate them smoothly to mono repo with submodule, Why not create a new clean monorepo, and then...

> Our problem is a little bit complicated: we have several public repos and several private repos, and we still want to maintain them with monorepo. This scenario makes sense...