Is it possible to configure baseUrl and still use relative path when doing autocomplete?

[lgraziani2712]

EDIT: since TS v4.1 baseUrl is not longer required to use with the paths rule, fixing this issue!

TypeScript Version: 3.7.4

Search Terms: baseUrl, autocomplete, relative path, lib, aliases, monorepo, sibling libs

Code

tsconfig.json

{
  "compilerOptions": {
    // ...

    "baseUrl": ".",
    "paths": {
      "sibling-a/lib/*": ["../sibling-a/src/*"],
      "sibling-b/lib/*": ["../sibling-b/src/*"]
    },
  },
  "references": [{ "path": "../sibling-a" }, { "path": "../sibling-b" }]
}

Expected behavior: I have a monorepo with some libs and some of them uses code from sibling libs. I achieved three things I wanted: (1) to not need to build them just for TS to correctly check the imports (thanks to baseUrl/paths config), (2) to jump into the actual definition instead of the built file (also thanks to baseUrl/paths), (3) to TS understand the relationship between these libs (although I don't know if I configured everything correctly).

The thing is, since I'm using the baseUrl config, any module I try to import from within the same library, but at least two folders up above the actual module will use the alias. E.g.:

// ./packages/sibling-c/src/some/path/to/file.ts
// I try to import
// ./packages/siblin-c/src/some/anotherFile.ts
// And instead of VSCode offering me
import anotherFile from '../../anotherFile';
// It will suggest something like this:
import anotherFile from 'src/anotherFile';

The problem with the alias for files withing the same lib is exactly that: they are libraries, so what I build with TS is what I publish to my private repository manager. When some service import the file with the alises it will crash because it won't understand it.

Is correct what I'm configuring/want to have?

Thank you in advance!

[typescript-bot]

This issue has been marked as 'Question' and has seen no recent activity. It has been automatically closed for house-keeping purposes. If you're still waiting on a response, questions are usually better suited to stackoverflow.

[Ore4444]

i second that. having the same issue. this is a bug

[andrewbranch]

You can suppress auto imports from using the unrooted path with a VS Code setting:

But TypeScript will still believe that src/anotherFile is valid. The proposal to “fix” this (it’s not actually a bug per se; my understanding is it used to be a feature designed for AMD modules and now that it’s being used differently by many people, certain aspects of the feature don’t make sense in the current context) is here: #31869.

[lgraziani2712]

Uhmmm, you really cannot use the relative value in a monorepo project. If that relativity only worked up to the nearest tsconfig file, maybe, but it isn't feasible to use it if it adds an import of a sibling lib's module as a relative import.

[andrewbranch]

FWIW, monorepos with project references work really well with lerna and/or yarn workspaces, and don’t require path mappings / baseUrl that way. Out of curiosity, how do you test/run the projects in your monorepo? That is, during development, what mechanism makes "sibling-a" resolve to ../sibling-a?