Invalid location in sourcemap


#1

We’re using Webpack to upload sourcemaps for every build, but I’m seeing many instances of “Invalid location in sourcemap.” The artifacts are definitely making it into their corresponding release. I’m not seeing any “NEW EVENTS” for the releases in the table under the releases tab, though.


#2

Just to make sure: you are generating the sourcemaps and the minified files in one step and there are no mismatches? Because webpack builds are not stable.


#3

Hi!

I’m not sure what you mean by mismatches. Also, can you clarify what you mean by “webpack builds are not stable?”


#4

I have seen that developers build a release once without sourcemaps and then a second time with sourcemaps afterwards. The generated minified files from the first run will not work with the second run that generated the sourcemaps.


#5

I see. In our case the build and upload are performed in the same release.


#6

I discovered that I had not configured the release parameter when initializing Raven. I now see events appearing in our releases. I suspect this will also help with the sourcemap issue. I’ll report back with my finding. Thanks for the help.


#7

Hey @etburke, did you find anything? I’m getting the same issue …


#8

“Invalid location in sourcemap” can happen if the sourcemap generated does not contain enough information is is incorrect. I would check that you are using production supported sourcemaps with line and column information and that they are propertly named so that the correct release is used.