-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
Input sourcemaps seem to not be honored #64
Comments
|
// @pofigizm |
It actually does not appear that you pass inputSourceMap into babel, so this would never be able to work as written. 😢 |
@bytenik, |
I confirm that it's broken. |
I can not reproduce. |
I just revisited this. Its true that your virtually identical gulpfile does not have the issue, whereas mine does. But the build task is line-for-line identical. I can confirm, however, that commenting out the
|
One diff which I found in deps is Can you extract a part of your project where the issue is reproduced? And push it? p.s. Magic does not exist! |
Just encountered problem, but: |
@asvetliakov, I can't reproduce it, too. |
I've just stumbled on this problem of invalid source maps. In general, I'm experiencing the same issues as other reporters do. I've tried to use gulp-babel on pretty complex Angular/TypeScript projects (15 of them in total) with very similar manifestations. In my case, sourcemaps are generated for each TypeScript file individually. In some cases sourcemaps were produced with two entries in sourcemap's After digging through gulp-babel code and babel documentation, I've come up with In cases when there is no input I tried to reproduce the problem with that github repo that you have provided, but without any luck. I guess, the problem manifests itself in more complex cases and I didn't found the actual thingy that triggers it. On the positive side, my implementation passes all tests currently provided in gulp-babel. Here is pull request |
I'm running gulp-typescript before piping through gulp-babel. I init sourcemaps before piping through TypeScript. The output source map from TypeScript seems to be ignored by gulp-babel. Babel itself does support input type maps.
Am I doing something wrong or is this a bug?
The text was updated successfully, but these errors were encountered: