Hopefully the last commit to this issue - changing the condition from '!==undefined' to '===null' required moving the check before the loop as the compared value is set and is no more null in the next iteration - the case worked for file mappings of length 1, for more entries it overwrites still the same source_map file.
thanpolas
commented
10 years ago
Hopefully the last commit to this issue - changing the condition from '!==undefined' to '===null' required moving the check before the loop as the compared value is set and is no more null in the next iteration - the case worked for file mappings of length 1, for more entries it overwrites still the same source_map file.