Incorrect Path Resolution for Type Imports in TypeScript Declarations

[xlianghang]

🔎 Search Terms

"specifier", "relative path"

🕗 Version & Regression Information

• This changed between versions 5.4.0-dev.20231221 and 5.4.0-dev.20231222
• This changed in commit or PR Add auto-import for the package.json imports field #55015

⏯ Playground Link

https://github.com/xlianghang/ts-specifier-bug

💻 Code

//src/main.ts
import { PartialType } from './utils';

class Common {}

export class Sub extends PartialType(Common) {
  id: string;
}

// src/utils/index.ts
import { MyType, MyReturnType } from './type-helpers';

export function PartialType<T>(classRef: MyType<T>) {
  abstract class PartialClassType {
    constructor() {}
  }

  return PartialClassType as MyReturnType;
}

// src/utils/type-helpers.ts
export type MyReturnType = {
  new (...args: any[]): any;
};

export interface MyType<T = any> extends Function {
  new (...args: any[]): T;
}

🙁 Actual behavior

The dist folder is not the root directory, so do not import from src

🙂 Expected behavior

Import from a relative path

Additional information about the issue

Compilation fails in the MacOS, but is expected to behave in the https://stackblitz.com/~/github.com/xlianghang/ts-specifier-bug

💻 MacOS 14.3，Apple M2 Max

[Boyban]

Got related problems, tRPC types inference in monorepo are not working since installing 5.4.0-dev.20231222.

I got any instead of my inferred types.

Additional information

💻 MacOS 14.3.1，Apple M3

[fatcerberus]

This is the second time a .d.ts emit bug has been traced to #55015: #57926 (comment)