Typescript build error file location

[julianklumpers]

Hi,

When building my app, when there is a TS error, it does not report the location of the file where the error is. We have a big repo, and it is a real pain to locate this error. Am I missing something?

[mwisnicki]

Same, it's very annoying.

[codeguru42]

I just encountered this as well. Text search in the project helps to narrow it down, but sometimes the same line of code appears in multiple places.

[tommck]

I have been having this problem for a while now. I'm new to React, so I thought it was pilot error, but I'm astonished that this isn't a higher priority. Is it rare to run across this?

[sahendrickson]

I don't get file names either. Are there plans to fix this? Is there a workaround?

[dennis-8]

Please fix it...

[c-bik]

+1

[trapgar]

This is still an issue 2 and-a-half years later! Though to be fair, the latest version of react-scripts was published 3 years ago... 🙄

Is this even under maintenance anymore? I'm not seeing any code changes in a long time; have all been docs/pipeline, but I am seeing at least 1 PR that addresses this issue.

[shimondoodkin]

+1

[shimondoodkin]

the build script was truncating the error message

main...shimondoodkin:create-react-app:shimondoodkin-error-filename

just edit the file
node_modules\react-scripts\scripts\build.js

about lines 173, make it like following, add for loop instead just if , then, length =1

  if (messages.errors.length) {
    // Only keep the first error. Others are often indicative
    // of the same problem, but confuse the reader with noise.
    const re = /\S+:\d+:\d+/;  // check if error message has filename with line number
    for(let i = 0; i < messages.errors.length; i++) {
      if(re.test(messages.errors[i])) {
        messages.errors.length = i+1; 
        break;
      }
    }
    return reject(new Error(messages.errors.join('\n\n')));
  }