Inconsistent tripple-slash directive in sub-directory

[icholy]

🔎 Search Terms

tripple-slash directives references

🕗 Version & Regression Information

v4.x did not emit these directives at all.

⏯ Playground Link

https://github.com/icholy/tsc-tripple-slash-bug

💻 Code

• src/types/fs.ts

declare module 'fs' {}

• src/a/x.ts

import * as fs from 'fs';

export { fs };

• src/a/b/x.ts

import * as fs from 'fs';

export { fs };

🙁 Actual behavior

Emitted files:

• lib/a/x.d.ts

/// <reference path="../types/fs.d.ts" />
/// <reference types="node/fs" />
import * as fs from 'fs';
export { fs };

• lib/a/b/x.d.ts (using types instead of path).

/// <reference types="lib/types/fs" />
/// <reference types="node/fs" />
import * as fs from 'fs';
export { fs };

🙂 Expected behavior

Emitted files:

• lib/a/x.d.ts

/// <reference path="../types/fs.d.ts" />
/// <reference types="node/fs" />
import * as fs from 'fs';
export { fs };

• lib/a/b/x.d.ts

/// <reference types="../../types/fs" />
/// <reference types="node/fs" />
import * as fs from 'fs';
export { fs };

Additional information about the issue

This seems to be related to module resolution.

[fatcerberus]

Looks like the same issue as #56571

[icholy]

@fatcerberus that does look like the same issue. But I'm not clear on why lib/a/x/d.ts outputs a path="..." directive while lib/a/b/x.d.ts outputs a types="..." directive?

[typescript-bot]

This issue has been marked as "Duplicate" and has seen no recent activity. It has been automatically closed for house-keeping purposes.

[icholy]

@RyanCavanaugh do you have any insight about why the two files contain different variations of the directive?