Imports breaking on >1.4.0

I’m upgrading the dependencies on my projects, and after upgrading tsc-alias (to 1.4.1 or 1.5.0), some of my imports are breaking.

The paths on my tsconfig is like this:

"paths": {
      "~/*": ["./*"]
    },

But this

import { Dispatch } from 'redux';

Is becoming

import { Dispatch } from '../../redux';

I think it’s because there is a redux folder on the folder it’s compiling, but it should not be parsed, as it does not begins with ~/

---

Another problem I had, was because some paths were not being parsed if an asset was not present (on the release script they were added afterwards)

This import was not parsed if the svg file was not present in the dist folder

export { default as iconx } from '~/assets/icons/iconx.svg';

[raouldeheer]

@ThiagoNP

I think it’s because there is a redux folder on the folder it’s compiling, but it should not be parsed, as it does not begins with ~/

This is probably because it’s resolving to the baseUrl. This could be solved by add a small config to tsconfig.json. More info on this is in issue #71

{
  "compilerOptions": {
    ...
  },
  "tsc-alias": {
    "replacers": {
      "base-url": {
        "enabled": false
      }
    }
  }
}

---

The second problem happens because tsc-alias checks if the file exists, because if it doesn’t it will use the next path in the array (in the tsconfig each path has an array of solutions). But this problem can be easily fixed by added dummy files so that the file exists and resolves.

[raouldeheer]

@justkey007 Maybe we should add a link to the F.A.Q. #110 in the readme?