- Development
Black Sand Solutions
Failed to parse SourceMap
7 October 2016By Rich @Black Sand Solutions
- Javascript
Ran in to this issue today. I added a missing source map to one of our dependencies and whilst Chrome could locate it, it could not parse it.
Failed to parse SourceMap
Ran in to this issue today. I added a missing source map to one of our dependencies and whilst Chrome could locate it, it could not parse it.
The problem was due to the file being saved in a format that Chrome does not read as a .map file.
The simple fix was to save the file using Visual Studio's File > Advanced Save Options
.
The file needs to be saved as Unicode (UTF-8 without signature)
or US-ASCII.
I found this tip on StackOverflow.