lowercase filename in triple slash directives

[gaurav5430]

Bug Report

Referencing a file name in triple slash directives automatically looks for the lower case filename

🔎 Search Terms

• triple slash directive
• lowercase filename

🕗 Version & Regression Information

have seen it since ts > 3.x

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about triple slash directives / lowercase filename

⏯ Playground Link

not sure how to reproduce it in the playground
This requires multiple files, and there is no easy way to verify

💻 Code

// fileOne.d.ts
...
...

// file2.d.ts
// <reference types="../fileOne.d.ts">
...
...

🙁 Actual behavior

on case sensitive OS, i got a warning from tscompiler about the casing being incorrect.

🙂 Expected behavior

should not get this warning

More Info:
I guess this is related to #26948
and it seems this is correct behaviour.

If that is the case, it would be great to document it alongside triple slash directives or add it to FAQs
https://www.typescriptlang.org/docs/handbook/triple-slash-directives.html

[DanielRosenwasser]

Do you have forceConsistentCasingInFileNames on?

[gaurav5430]

Yes, it is on

[DanielRosenwasser]

Sorry, I misread the issue - I don't know if that's actually relevant, though it does help avoid the issue.

If the underlying file is fileone.d.ts, on a case-sensitive system, this behavior is actually expected. Is that correct? The original post doesn't seem to give a full repro.

[gaurav5430]

yes, my point is more about the fact that it seems the triple slash directives by default convert all filenames to lowercase, but that is not documented anywhere

[BPapp-MS]

This bug broke a couple pipelines for us the other day- it seems that compilation on an OS which is case insensitive produces reference tags in d.ts files which are lowercase, whereas on an OS which is case-sensitive it maintains proper casing in the output. Failures were caused when we started validating the reference directives in the generated API document, and there was platform-based mismatch. It seems unnecessary to lowercase the path on case-insensitive platforms in the first place.

[BPapp-MS]

Example source:

// src/source.tsx
/// < reference path="./ReferencedTypes.d.ts" />

Compiled declaration file in Unix (case sensitive):

// lib-esm/source.d.ts
/// < reference types="./ReferencedTypes.d.ts" />

Generated declaration file in Windows (case insensitive):

// lib-esm/source.d.ts
/// < reference types="./referencedtypes.d.ts" />

[RyanCavanaugh]

/// < reference types="./ReferencedTypes.d.ts" />

I'm not sure how you got into a state where a relative path directive got updated to a types directive (I'm sure it's possible but don't know how to reconstruct that). Can you share a complete repro?

[fatcerberus]

yes, my point is more about the fact that it seems the triple slash directives by default convert all filenames to lowercase

You said the underlying file is lowercase. I don't think it's a blind conversion like you suggest--it's observing that the filename in the directive doesn't match what's on disk and warning you about that. Blindly converting all filenames to lowercase wouldn't make sense and would actually break things on a case-sensitive FS.

[gaurav5430]

yes, my point is more about the fact that it seems the triple slash directives by default convert all filenames to lowercase

You said the underlying file is lowercase. I don't think it's a blind conversion like you suggest--it's observing that the filename in the directive doesn't match what's on disk and warning you about that. Blindly converting all filenames to lowercase wouldn't make sense and would actually break things on a case-sensitive FS.

Hey, not really, that's not what I meant.

the underlying file name is fileOne.d.ts created on Mac OS
and on Mac OS it works alright if I have a
<reference path="./fileOne.d.ts" />

but it gives an error on Linux about inconsistent casing

[Uzlopak]

We got today a Bug Report on mongoose by @Davis-owen regarding this bug. This is totally undocumented and unexpected behavior.

I think the bug was introduced with #10340 by @Andy-MS when the lowercasing was only about the npm package name.

I think that the solution is to check if it is a string, which does not contain a slash "/" and lowercase it, and if it contains a slash to split the string and only lowercase the the first part and keep the rest unchanged. Or maybe even remove the lowercasing. It was imho in the first place wrong, to implicitly transform the reference path to lowercase.

[Uzlopak]

Here again a proof, that the lowercase is because of that PR which was only targetting to lowercase the npm package name.

s-panferov/awesome-typescript-loader#326 (comment)
by @DanielFallon

As of that merge, all reference tags are used as lowercase'd