Anton Gilgur

Yea I noticed from #447 😅 ESM adoption has (expectedly) caused a bit of churn in the ecosystem. Though this PR specifically only needs to update all the Rollup deps,...

So CJS and Rollup's CJS option have been available long before `.cts` or `.cjs`. As such, any logic would have to be able to output with different file endings. We...

I was more thinking in the opposite direction -- tools that don't yet support `.cts` would break. For example, if a user has a declaration processor plugin after rpt2, this...

> how can I set the generated `index.d.ts` file to be called `index.d.cts` instead? So there is potentially a small problem here. If your input is `index.mts`, TypeScript would _only_...

I'll need to look into this more as it's been a while since I've seen this kind of issue, but really quick off the top of my head (and on...

Oh there are indeed some complications in your case. I see you have configured [TS `paths`](https://github.com/lavcraft/rollup-typescript-project-references-example-problems/blob/b0d96f5315c2c4298018730e0cc4e6bd082c42ef/packages/sdk/tsconfig.json#L29), and that it goes up two directories. That would indeed set your `rootDir` to...

> In rollup variant number 2 we will see next error: > > ``` > > [!] (plugin rpt2) RollupError: src/actions/create.ts:1:20 - error TS6059: File '/rollup-ws-problem/packages/shared/src/test/util.ts' is not under 'rootDir'...

### goal? in-lining? > In my example with rollup, shared workspace sources are inlined into the resulting sdk perfectly. > inline all my shared d.ts Ah ok, so you are...

OH. I got it to work. > As a note, it had this behavior even when I removed the aliases and just manually referenced the other project, so this does...

> That mean, i wan't to use ts project reference for use rollup `dev mode` and auto build dependencies and caching. If i change `paths.@shared` from `../../shared/src/*` to `../../shared/build/*` i...