Babel-loader: Console stack trace length

Created on 6 Jul 2015  路  3Comments  路  Source: babel/babel-loader

Currently the stack trace on a parser error is ungodly long. Is there a way to suppress the output to only show the syntax error and relevant lines?

Ex:

ERROR in ./src/Sources.js
Module build failed: SyntaxError: C:/Users/matt/Data Visualization/DataVisualizationTool/Scripts/components/src/Sources.js: Unexpected token
 (42:6)
  40 |       // status not 200, known limitation of jsonp
  41 |       //
> 42 |       error: errorCallback,
     |       ^
  43 |     })
  44 |   }
  45 |
    at Parser.pp.raise (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\acorn\src\loca
tion.js:80:13)
    at Parser.pp.unexpected (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\acorn\src
\parseutil.js:95:8)
    at Parser.pp.expect (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\acorn\src\par
seutil.js:89:26)
    at Parser.pp.parseObj (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\acorn\src\e
xpression.js:582:12)
    at Parser.pp.parseExprAtom (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\acorn\
src\expression.js:385:19)
    at Parser.parseExprAtom (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\node_modules\
acorn-jsx\inject.js:373:24)
    at Parser.pp.parseExprSubscripts (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\
acorn\src\expression.js:232:19)
    at Parser.pp.parseMaybeUnary (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\acor
n\src\expression.js:214:19)
    at Parser.pp.parseExprOps (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\acorn\s
rc\expression.js:170:19)
    at Parser.pp.parseMaybeConditional (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\li
b\acorn\src\expression.js:153:19)
    at Parser.pp.parseMaybeAssign (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\aco
rn\src\expression.js:121:19)
    at Parser.pp.parseExprList (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\acorn\
src\expression.js:769:124)
    at Parser.pp.parseSubscripts (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\acor
n\src\expression.js:259:27)
    at Parser.pp.parseSubscripts (C:\Users\matt\Data Visualization\DataVisualizationTool\Scripts\components\node_modules\babel-core\lib\acor
n\src\expression.js:248:17)



.... Omitting the other ~40 lines for brevity

 @ ./src/DataSetList.js 23:15-35
    + 276 hidden modules

Most helpful comment

@enjoylife Can you add your solution to this issue? I'm having the same problem

All 3 comments

@enjoylife are you able to solve this problem? :)

Yeah this was a configuration issue I believe

@enjoylife Can you add your solution to this issue? I'm having the same problem

Was this page helpful?
0 / 5 - 0 ratings