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
I've generally used this package with a config that uses an outDir, however I gave outFile a shot and noticed a few misses!
In a project where I had a folder named types with an index.ts, my import is import types from "~types". When I build this to a single declaration file with outFile, the import is (in certain places) converted to import("types"), rather than `import("types/index").
The types are being processed, but perhaps incorrectly.
It's always where the type is imported "inline" as shown:
I've generally used this package with a config that uses an
outDir
, however I gaveoutFile
a shot and noticed a few misses!In a project where I had a folder named
types
with anindex.ts
, my import isimport types from "~types"
. When I build this to a single declaration file withoutFile
, the import is (in certain places) converted toimport("types")
, rather than `import("types/index").The types are being processed, but perhaps incorrectly.
It's always where the type is imported "inline" as shown:
The correct result would be:
Without
tsconfig-replace-paths
, I get:Which also shows an error.
Another example where the import is resolved to
./types
rather thantypes/index
.(P.S. Thanks for this package, it's great!)
The text was updated successfully, but these errors were encountered: