Support big TypeScript projects

In my TypeScript codebase I have a folder structure like this:

src
  module1/index.ts
  	...
  module2/index.ts
	...

My tsconfig.json looks like this:

{
  "compilerOptions": {
    "rootDir": "src",
    "outDir": "dist"
  }
}

When running ncc src/module1/index.ts -o module, it also builds the dist folder into it, including module2.
The output in ./module1 looks like this:

module1
  dist/...
  module2/...
  module1/...
  index.d.ts
  index.js

What do you think is the most elegant way to fix this?

One possibility would be providing a path to a tsconfig.json file.
In that tsconfig.json file I then could provide "rootDir": "src/module" - that would already help. But still it would be great if dist would not be copied over.

For now, I'm manually cleaning up ./module1 as I don't want to ship that clutter.

Thanks!

Start by reproducing ncc src/module1/index.ts -o module with the shown src layout and tsconfig.json. Trace how the ncc entry point handles TypeScript project files and output paths. Done means building one module no longer copies dist or sibling module2 content into the output.