You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Please upgrade source-map to 0.7.2 to get speed improvements #144
I'm open to help on this front, if you feel like taking a look. I can also look into whether it would be easier to update in nyc first (which has its own implementation of source-map handling).
@andreicristianpetcu Just want to mention I've upgraded source-map from 0.5 to 0.6 (in master, not yet released). I didn't try updating to 0.7 because it says that it requires node.js 8 while node.js 6 isn't EOL for another 10 months.
I've looked into this and think it's impossible. nyc needs to process source-map's during process exit hooks where code must be sync. Unless a future version of source-map finds a way to support a sync API we will never be able to upgrade.
Activity
bcoe commentedon Mar 4, 2018
@andreicristianpetcu the new soure-map API is unfortunately async, which would require a fairly major refector of the Istanbul API to support:
https://github.com/mozilla/source-map/blob/master/CHANGELOG.md#070
I'm open to help on this front, if you feel like taking a look. I can also look into whether it would be easier to update in nyc first (which has its own implementation of source-map handling).
coreyfarrell commentedon Jun 5, 2018
@andreicristianpetcu Just want to mention I've upgraded source-map from 0.5 to 0.6 (in master, not yet released). I didn't try updating to 0.7 because it says that it requires node.js 8 while node.js 6 isn't EOL for another 10 months.
coreyfarrell commentedon May 6, 2019
I've looked into this and think it's impossible. nyc needs to process source-map's during process exit hooks where code must be sync. Unless a future version of source-map finds a way to support a sync API we will never be able to upgrade.
fix: use lenient matching for coverage merge when end.column differs