Skip to content

Errors emitted by react-scripts build don't include any trace after upgrading to 5.0.0 #12043

Open
@corymharper

Description

@corymharper

I'm not sure if this is a bug or intended so I've marked it as a question for now...

I am upgrading an application from 4.0.3 to 5.0.0, one thing we noticed immediately however, is that build errors no longer include any kind of file trace with them, here's an example:

4.0.3:

/src/components/app.tsx
TypeScript error in /src/components/app.tsx(22,2):
'faPaperPlane' is declared but its value is never read.  TS6133

    20 | import { FontAwesomeIcon } from '@fortawesome/react-fontawesome';
    21 | import {
  > 22 | 	faPaperPlane,
       | 	^
    23 | 	faHandPointRight,
    24 | 	faLocationCircle,
    25 | 	faKey,

5.0.0

TS6133: 'faPaperPlane' is declared but its value is never read.
    20 | import { FontAwesomeIcon } from '@fortawesome/react-fontawesome';
    21 | import {
  > 22 | 	faPaperPlane,
       | 	^^^^^^^^^^^^
    23 | 	faHandPointRight,
    24 | 	faLocationCircle,
    25 | 	faKey,

The former is a lot more convenient to debug than the latter, and I'm not sure what about upgrading has caused the error to be less verbose, but is there something I'm missing, or a change I need to make since upgrading?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions