Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Command line scripts - wrong error line number

See original GitHub issue

👋

I just noticed that if I have:

#!/usr/bin/env node

on top of my file, the error line is not the correct one. The error message itself is correct but the error line number is the next one after the actual error.

Issue Analytics

State:
Created 8 years ago
Comments:7 (1 by maintainers)

Top GitHub Comments

3reactions

laggingreflexcommented, Nov 19, 2015

I was too facing this just now. Line number off by 2.

However retainLines: 'true' (in babel options) seem to solve it.

I’m suspecting babel-polyfill or some other helper function is injecting extra 2 lines.

Funnily I was trying to get rid of that retainLines option with this library. great succes/s!

0reactions

hollowdoorcommented, Dec 19, 2016

I was just passing by, and I thought maybe since this is a command line script you’re making that this might be a conflict with how node works. Before node runs a command script it removes the shebang from the script’s string. That might put your error off by one line.