You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Emitting combined output declarations tries to resolve monorepo imports #39547
Strangely enough, when omitting the --outFile flag, the declaration file for packages/a/src/index.ts (correctly) contains import ... from "b"; (this suggests that this is indeed a bug and not per design).
I just noticed that import .. from "./b" and import ... from "b" are (independent from this issue) both transpiled to "b" in the declarations output....
Activity
mischnic commentedon Jul 10, 2020
(I'd be happy to fix this myself if someone can confirm this and point me to the right source files)
RyanCavanaugh commentedon Jul 15, 2020
Using
outFilewith modules is almost always a mistake; what are you intending to do with that setting?mischnic commentedon Jul 15, 2020
Thanks for the response!
We're using it in Parcel to essentially create a definitions bundle (as opposed to multiple files) for a package, e.g.
--tsc-->
--ast transformation-->
(https://github.com/parcel-bundler/parcel/blob/1f5586657f1ea8660ca1f06abdd75687851ebbb2/packages/transformers/typescript-types/src/TSTypesTransformer.js#L28-L69)
EDIT:
I just noticed that
import .. from "./b"andimport ... from "b"are (independent from this issue) both transpiled to"b"in the declarations output....