{"action":"closed","issue":{"url":"https://api.github.com/repos/huston007/ng-annotate-loader/issues/10","labels_url":"https://api.github.com/repos/huston007/ng-annotate-loader/issues/10/labels{/name}","comments_url":"https://api.github.com/repos/huston007/ng-annotate-loader/issues/10/comments","events_url":"https://api.github.com/repos/huston007/ng-annotate-loader/issues/10/events","html_url":"https://github.com/huston007/ng-annotate-loader/issues/10","id":104586787,"number":10,"title":"Incorrect chained source maps","user":{"login":"jvmccarthy","id":1642221,"avatar_url":"https://avatars.githubusercontent.com/u/1642221?v=3","gravatar_id":"","url":"https://api.github.com/users/jvmccarthy","html_url":"https://github.com/jvmccarthy","followers_url":"https://api.github.com/users/jvmccarthy/followers","following_url":"https://api.github.com/users/jvmccarthy/following{/other_user}","gists_url":"https://api.github.com/users/jvmccarthy/gists{/gist_id}","starred_url":"https://api.github.com/users/jvmccarthy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jvmccarthy/subscriptions","organizations_url":"https://api.github.com/users/jvmccarthy/orgs","repos_url":"https://api.github.com/users/jvmccarthy/repos","events_url":"https://api.github.com/users/jvmccarthy/events{/privacy}","received_events_url":"https://api.github.com/users/jvmccarthy/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":15,"created_at":"2015-09-02T22:46:07Z","updated_at":"2015-09-05T21:09:26Z","closed_at":"2015-09-05T21:09:26Z","body":"First, thank you for creating this much-needed loader.\r\n\r\nI'm having an issue right now where source map line numbers aren't lining up after running the ng-annotate-loader.  I've been having difficulty debugging because placing breakpoints in the Chrome debugger don't land on the correct line.  Because the line numbers are off, stepping in the debugger isn't working either.\r\n\r\nJust looking into source maps is difficult for that matter.  I found that by opening my generated webpack bundle, I can click to place a breakpoint and Chrome will take me to the mapped line in the source map.  Using this technique, I can tell the source map becomes incorrect after the first ng-annotate addition (after a line containing `$inject`).  I've also tested removing the ng-annotate-loader, and then I get correct source mappings.  The lines appear shifted for each line ng-annotate adds, as if the source map isn't being altered at all by ng-annotate.\r\n\r\nI'm using ng-annotate-loader chained with the babel-loader like this,\r\n````javascript\r\n{ test: /\\.js$/, loader: 'ng-annotate!babel' },\r\n````\r\nwith `devtool: 'source-map'`\r\n\r\nI can appreciate that ng-annotate-loader is the middleman here and that this may be an ng-annotate issue.  I've tried a number of different things including rolling back to ng-annotate-loader@0.0.4 or rolling to ng-annotate@1.0.2 and source-map@0.4.4 (the current latest versions).  No combination seems to work.  I've also tried debugging a bit in `loader.js`, but I get lost trying to compare the merged map from the original.\r\n\r\nAny suggestions would be appreciated.  Is there a quick way I can debug if ng-annotate isn't generating a proper source map?  The plumbing in ng-annotate-loader looks right, but I'm not sure.  I thought I would start here first.\r\n\r\nThanks!"}}