`baseUrl` is not respected

[MichaelMitchell-at]

Instructions:
Create the following directory structure:

• tsconfig.json

{
  "compilerOptions": {
    "noEmit": true,
    "baseUrl": "."
  }
}

• index.ts

export {type A} from 'internal/utils';

• internal
  • utils.ts

  export type A = {};

Expected behavior:

$ tsc
# no error

Actual behavior

$ tsgo tsc
index.ts(1,24): error TS2307: Cannot find module 'internal/utils' or its corresponding type declarations.

[andrewbranch]

This is intentional because I plan to deprecate it in 6.0.

[MichaelMitchell-at]

This is intentional because I plan to deprecate it in 6.0.

@andrewbranch Will custom bare module specifier import paths no longer be supported or will there be an alternative mechanism to baseUrl? Will a migration to using relative paths be needed? Having root-relative import paths is hugely beneficial to code migrations since moving a file/directory from A to B is as straightforward as

sed -i -e "s| from 'A/| from 'B/|g"

Feel free to move this comment if this is not the right place to discuss.

[MichaelMitchell-at]

I may have just answered my question upon discovering that tsgo seems to allow tsconfig.json to have

    "paths": {
      "*": ["*"]
    }

without a baseUrl set. This was previously disallowed by tsc (Strada). I haven't completely looked into the implications, but if this is sufficient to replicate the old behavior, then I suppose there's no cause for alarm.

[andrewbranch]

That’s been the case since TS 4.1 😄 https://www.typescriptlang.org/docs/handbook/modules/reference.html#baseurl