Make transport Jest-aware

[mcollina]

Fixes #1179

[JaneJeon]

I’ll try it with this PR, see if my CI still fails

[JaneJeon]

Beautiful, works perfectly (both locally and on CI)!

[jsumners]

I really don't want to approve this. It seems more like a bug in another package to me. But I'm not blocking it.

[mcollina]

I really don't want to approve this. It seems more like a bug in another package to me. But I'm not blocking it.

I'm with you, but I do not see any other way to fix it. It's a massive design flaw in Jest and part of the enormous technical debt they push on the rest of the ecosystem.

I do not feel we should spend energy to make a stand against jest. My twitter rants about it are enough. Let's land this and move on :(.

[mcollina]

@jsumners I've found a better fix for this.

[JaneJeon]

@mcollina oh cool, so my suggestion DID work!

[davidmarkclements]

struck out below was written with the old solution in mind, should have checked the new one first. Since it it isn't specific to Jest it's an acceptable workaround for us. However, as a general rule, the points below still stand.

for the record I'm also against doing this.
I think we should revert.
This is a Jest issue, we cannot and should not cover for Jest, doing so just takes away any political will for Jest to fix it.

[jsumners]

Since it it isn't specific to Jest it's an acceptable workaround for us. However, as a general rule, the points below still stand.

I argue it is still specific to Jest. We have to keep the comment in the code explaining why the import is being done the way it is specifically because of Jest.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.