|
sfcode
An Online Competing and Development Environment
|
SourceMapConsumer. Read about it here: http://fitzgeraldnick.com/2018/02/26/speed-without-wizardry.htmlSourceMapConsumer now uses WebAssembly, and is much faster! Read about it here: https://hacks.mozilla.org/2018/01/oxidizing-source-maps-with-rust-and-webassembly/new SourceMapConsumer now returns a Promise object that resolves to the newly constructed SourceMapConsumer instance, rather than returning the new instance immediately.SourceMapConsumer instance, you must call SourceMapConsumer.prototype.destroy on it. After calling destroy, you must not use the instance again.SourceMapConsumer used to be able to handle lines, columns numbers and source and name indices up to 2^53 - 1 (aka Number.MAX_SAFE_INTEGER). It can now only handle them up to 2^32 - 1.source-map library now uses modern ECMAScript-isms: let, arrow functions, async, etc. Use Babel to compile it down to ECMAScript 5 if you need to support older JavaScript environments.files. See issue #212.SourceMapConsumer.prototype.sourceContentFor and sources that explicitly start with the source root. See issue #199.SourceMapGenerator after having created a SourceMapConsumer from it via SourceMapConsumer.fromSourceMap failed. See issue #191.SourceMapGenerator would mistakenly consider different mappings as duplicates of each other and avoid generating them. See issue #192.SourceMapConsumer.prototype.allGeneratedPositionsFor and fuzzy searching in the presence of a column option. See issue #177.SourceMapConsumer.prototype.hasContentsOfAllSources method to determine when all sources' contents are inlined into the source map. See issue #190..npmignore file so that the benchmarks aren't pulled down by dependent projects. Issue #169.column argument to SourceMapConsumer.prototype.allGeneratedPositionsFor and better handle lines with no mappings. Issues #172 and #173.bias option you can supply to SourceMapConsumer to control the fuzzy searching direction. See #167.SourceMapConsumer.prototype methods.SourceMapGenerator and SourceNode. See issue #148 for some discussion and issues #150, #151, and #152 for implementations.SourceNodes from different versions of the source-map library couldn't be used in conjunction with each other. See issue #142.SourceMapConsumer.prototype.computeColumnSpans method to compute the column span of each mapping.SourceMapConsumer.prototype.allGeneratedPositionsFor method to find all generated positions associated with a given original source and line.names mapping property to be an empty string. Issue #121.SourceNode.fromStringWithSourceMap to specify a path that relative sources in the second parameter should be relative to. Issue #105.SourceMapGenerator, then the resulting source map will no longer have a null file property. The property will simply not exist. Issue #104.SourceNodes. Issue #116.SourceNode work with windows style ("\r\n") newlines. Issue #103.SourceMapGenerator.prototype.applySourceMap. Issue #100.SourceMapGenerator.prototype.applySourceMap.SourceNode.prototype.walk and SourceMapConsumer.prototype.eachMapping.SourceMapGenerator.names and sources arrays of source maps (usually from TypeScript) we are parsing. Fixes github issue 72.file property is missing in SourceMapConsumer, we don't use it anyway.file:// URIs. See https://bugzilla.mozilla.org/show_bug.cgi?id=885597