[Feature]: upgrade source-map to @cspotcode/source-map

[cspotcode]

🚀 Feature Proposal

Is there any interest in upgrading from source-map to @cspotcode/source-map? If so, I can attempt a pull request to see if all the tests pass.

Motivation

I see it mentioned in a few places that jest is blocked from upgrading past source-map 0.6.1.

mozilla/source-map#331 (comment)
https://github.com/facebook/jest/blob/199f9811ae68b15879cbe18b7ef7ebd61eefcf23/packages/jest-transform/src/types.ts#L29

@cspotcode/source-map has a sync API but the improved WASM-enabled performance of newer source-map.

Example

No response

Pitch

It would improve performance. By how much, I'm not sure.

[cspotcode]

I ran the tests locally, but not the mercurial tests, since it seems like they are always failing: #8653

They are passing, so I submitted #12486 to allow you to run the full test suite if you want.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[SimenB]

Happy to test this out after cspotcode/node-source-map-support#37 lands 👍

[SimenB]

Or rather, migrate to using @cspotcode/source-map-support

[cspotcode]

Oh I thought this was superceded by the switch to trace-mapping. Does jest use source-map-support, which hooks the node runtime to rewrite stack traces? I thought it only used source-map -- now trace-mapping -- the underlying sourcemap library. Boy these names can get confusing. EDIT: Nevermind, now I remember we've talked about this and it *is* used. I guess I'm becoming forgetful. I hopefully have time for this over the weekend.

…

On Thu, Apr 21, 2022, 6:55 AM Simen Bekkhus ***@***.***> wrote: Or rather, migrate to using @cspotcode/source-map-support — Reply to this email directly, view it on GitHub <#12485 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC35OATGQEANCK54AKG7W3VGEX3PANCNFSM5PGGJEPA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[SimenB]

Yep, that sounds right 😀

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.