Open transitive-bullshit opened 4 years ago
TSDX uses rollup-plugin-typescript2
under-the-hood. This sounds like and the error looks to be upstream there
Thanks, Anton; seems related: https://github.com/ezolenko/rollup-plugin-typescript2/issues/112
Current Behavior
composite
projects don't appear to be recognized properly. Here's an example top-level composite config from notion-kit:If you run
tsdx build
on either the root directory containing the compositetsconfig.json
, it creates empty output for the composite project.If you try to run
tsdx build
on one of the concrete sub-projects,tsdx
fails with an opaque error message:Note that this fairly simple set of
composite
packages works when compiled directly withtsc
.Versions
node: v14.5.0
"tsdx": "^0.13.3", "tslib": "^2.0.1", "typescript": "^4.0.2",
Desired Behavior
I'd love for
tsdx
to work in this case just like if I rantsc
on this config. E.g., it would build the sub-projects to their respective output folders, taking into account inter-package dependencies.Who does this impact? Who is this for?
Monorepo package library authors for medium to large-sized projects. People using
lerna
andcomposite
TS projects.Describe alternatives you've considered
Currently, I'm just outputting
commonjs
packages. I really need to output bothesm
andcommonjs
modules for these packages, so I'm considering adding a two-phase build for production, but it's awkward and one of the core reasonstsdx
was built in the first place.Also, it's entirely possible that I'm missing something obvious or messing something up on my end.
Thanks!