how stable is the current impl for `per-file` gran...
# javascript
f
how stable is the current impl for
per-file
granularity? i'm considering use of it with imports directly to the separate generated modules and types via export map (avoiding the root module import that aggregates and re-exports the modules) to aid with tree-shaking, for which this approach has shown really significant improvements in a library i'm working on. just wondering if this might be a fairly safe thing to do or i'm just going to cause myself a lot of deferred pain 😁
e
If you're planning to import the generated code into another TS package, keep in mind
per-file
doesn't output
d.ts
files that link to each other yet.
At the moment I'm still using
per-module
, however
per-file
is going to solve a bunch of issues once it's stabilized.