Version 0.5.3 (2019-12-28)
 
 
 - Fixed: base64 encoded source maps now correctly decodes as utf-8. Previously,
 non-ASCII characters could end up garbled. Thanks to ZHAO Jinxiang
 (@xiaoxiangmoe)! (Note: This fix does not work in old evironments not
 supporting bothTextDecoderandUint8Array.)
- Improved: Reduced size of the npm package.
Version 0.5.2 (2018-05-10)
 
Version 0.5.1 (2017-10-21)
 
 
 - Fixed: URLs are now decoded before being passed to readin Node.js. This
 allows reading files with spaces, for example.
- Fixed: Missing or empty sourcesfields (such assources: []) in source
 maps are now handled. Previously, such source maps would cause crashes or
 callbacks never bing called. Now, an empty result is produced:
js sourcesResolved: [], sourcesContent: [] 
Version 0.5.0 (2016-02-28)
 
 
 - Improved: Errors now have a sourceMapDataproperty that contain as much as
 possible of the intended result of the function up until the error occurred.
- Changed: resolveSourcesandresolve, as well as their*Sync
 alternatives, no longer fail when one single source fails to be fetched.
 Instead, thesourcesContentarray in the result object will contain error
 objects for all failed sources, and strings otherwise. (Backwards-incompatible
 change.)
Version 0.4.0 (2015-08-29)
 
 
 - Removed: The ignoreSourceRootoption ofresolveSources. It has been
 replaced withsourceRoot: false. (Backwards-incompatible change.)
- Added: The sourceRootoption ofresolveSources. It not only allows to
 ignore the source root, it also lets you replace it.
- Added: The parseMapToJSONmethod.
- Added: The resolvemethod now acceptsnull, mapUrl, ...as arguments, in
 addition to the existing signature, which will readmapUrlinstead of
 looking for a sourceMappingURL in the code.
Version 0.3.1 (2014-08-16)
 
 
 - Improved: Updated the source-map-url dependency to 0.3.0.
Version 0.3.0 (2014-07-02)
 
 
 - Removed: Argument checking. It’s not worth it. (Possibly
 backwards-incompatible change.)
- Added: The sourceRootproperty of source maps may now be ignored, which can
 be useful when resolving sources outside of the browser.
- Added: It is now possible to resolve only the URLs of sources, without
 reading them.
Version 0.2.0 (2014-06-22)
 
 
 - Changed: The result of resolveSourcesis now an object, not an array. The
 old result array is available in thesourcesContentproperty.
 (Backwards-incompatible change.)
- Changed: sourceshas been renamed tosourcesContentin the result object
 ofresolve. (Backwards-incompatible change.)
- Added: resolveSourcesnow also returns all sources fully resolved, in the
 sourcesResolvedproperty.
- Added: The result object of resolvenow contains thesourcesResolved
 property fromresolveSources.
Version 0.1.4 (2014-06-16)
 
 
 - Fixed: sourcesContentwas mis-typed assourceContents, which meant that
 thesourcesContentproperty of source maps never was used when resolving
 sources.
Version 0.1.3 (2014-05-06)
 
 
 - Only documentation and meta-data changes.
Version 0.1.2 (2014-03-23)
 
 
 - Improved: Source maps starting with )]}'are now parsed correctly. The spec
 allows source maps to start with that character sequence to prevent XSSI
 attacks.
Version 0.1.1 (2014-03-06)
 
 
 - Improved: Make sourceRoot resolving more sensible.
A source root such as /scripts/subdir is now treated as /scripts/subdir/
 — that is, as a directory called “subdir”, not a file called “subdir”.
 Pointing to a file as source root does not makes sense.
Version 0.1.0 (2014-03-03)