-
Notifications
You must be signed in to change notification settings - Fork 70
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.
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
Source maps problem #15
Comments
I've got the same issue @gpbl, did you figure this out or an alternative? |
@niftylettuce not yet :( |
Perhaps it is related to this babel/example-node-server#10 (comment) - you can just use |
@niftylettuce @gpbl sorry for very late response. So @niftylettuce answer is correct (at least it could be one of the reasons you may be seeing this) – this problem may occur if you import I'll prepare a patch that will give you a warning whenever that thing happens. I don't think we can ever circumvent this, but at least we can make it cleaner for the users to understand what's going on. Thanks @gpbl for reporting and @niftylettuce for investigating this issue and for your answer |
Have a fix for that here: 6ea1c10 |
And I've just pushed an update to npmjs, please check 2.0.3-rc0 and reopen if you're still experiencing the issue |
Hi, first thanks for this module, it made my restarts much faster 👍
However, my error stack traces show wrong line numbers. If i run the app with
babel-node --source-maps
the line numbers are correct. Does anybody else have this issue?The text was updated successfully, but these errors were encountered: