tsc-alias icon indicating copy to clipboard operation
tsc-alias copied to clipboard

Replace alias paths with relative paths after typescript compilation

Results 37 tsc-alias issues
Sort by recently updated
recently updated
newest added

Hi, thank you so much for this amazing lib :) Everything works fine when using 1.6.4 I get `tsc-alias info: 94 files were affected!` But when I switch to 1.6.5...

Hi, My problem is that ts-alias never replaces any import because it resolves to an invalid path. All paths resolve to /goui/dist/... instead of /goui/dist... I have this tsconfig: ```...

Reproducible in this project https://github.com/seamapi/types at this commit: https://github.com/seamapi/types/commit/68ec4828c2c835d1a0694185d6dcd01fa2fe0a5b Project defines [paths](https://github.com/seamapi/types/blob/68ec4828c2c835d1a0694185d6dcd01fa2fe0a5b/tsconfig.json#L26-L31) as ```json { "paths": { "@seamapi/types": ["./src/index.ts"], "@seamapi/types/connect": ["./src/connect.ts"], "@seamapi/types/devicedb": ["./src/devicedb.ts"], "lib/*": ["./src/lib/*"] } } ``` And has...

I have a file `stripe.ts` which imports the `stripe` module (npm install stripe). tsc-alias adds a .js extension to it for some reason. ``` // stripe.ts import Stripe from "stripe"...

There is an error in not parsing the path accurately, depending on the `baseUrl` value in `tsconfig.json`. # Error Case - `tsconfig.json` ```json { ... "compilerOptions": { "baseUrl": "./src/jslib", "paths":...

**TL; DR:** When an aliased subdirectory has the same name as the project folder, tsc-alias can fail to replace import aliases, causing imports to fail at runtime. I use `tsc-alias`...

Hello guys, i have problem 🙏 I have a local module which is located in node_modules, such ⤵️ cd lib-A yarn add link:../lib-B When another project uses it in its...

I have a file named `axios.ts` . If any file includes `import axios from "axios"` in the same directory, it will be replaced to `const axios_1 = require("./axios")`, not use...

when tsconfig.json has `allowJS:true`, then the emitted files contains many `.js` files, these files' path don't get transpiled in `require()` statement.

All replacements get reported as `Invalid path` in the debug output. I suspect that the resolver tries to check the existence of the target file. When replacing in a declaration...