Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Is it possible to map error traces back to source files? #190

Open
benjamingorman opened this issue Jun 30, 2020 · 0 comments
Open

Is it possible to map error traces back to source files? #190

benjamingorman opened this issue Jun 30, 2020 · 0 comments

Comments

@benjamingorman
Copy link

benjamingorman commented Jun 30, 2020 •
edited
Loading

Hi, I'm using grunt-contrib-concat and have a question: Is there some way to map line numbers from an error stack trace back to the line number in the original source file pre-concatenation? Currently the stack traces I get just mention a line number in the concatenated file, but for ease of debugging I would prefer to see the number from the original file pre-concatenation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@benjamingorman