-
Notifications
You must be signed in to change notification settings - Fork 150
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
Feature request: Sourcemaps support #49
Comments
Yup. I will be happy merge a source maps PR! |
👍 Need! |
👍 |
I have a mostly working implementation for basic sourcemaps. (No merging of existing sourcemaps, at least for now. gulp-ng-annotate should be able to handle that at least) I'll try and clean it up for a PR! |
Merged and will be part of 0.9.9 |
👍 |
0.9.9 is released |
Thanks! |
Does this support sourcemaps created using gulp/grunt where we concat, ngannotate, and uglify and add sourcemaps? I'm seeing the line numbers being off in chrome. |
@johnpapa No, AFAIK it doesn't consume input source maps for now. |
Re incorrect line numbers, can you please open an issue with test data? I will merge further improvements to source maps, especially input support. Keep those PR's coming! =) |
Same as @johnpapa. ngAnotate = require('gulp-ng-annotate'), chrome developer tools points me to different file and place in it :/ Without ng-annotate it works correctly! :/ |
I'm currently looking into this. I think it has something to do with the You can see what's going on with your particular files by visualizing the sourcemap output using this tool: http://sokra.github.io/source-map-visualization/ |
Is anyone using Kagami/gulp-ng-annotate ? If so, would you mind sharing an example Gulpfile & package.json? |
ng-annotate lacks support for (inline) sourcemaps. Pointed here from gulp-ng-annotate: Kagami/gulp-ng-annotate#3
Nicest solution would be to update inline sourcemaps similar to autoprefixer: https://github.com/ai/autoprefixer#source-map ?
The text was updated successfully, but these errors were encountered: