OJ Kwon

@kdy1 one more: weirdly, this seems only happening on the debug build. 🤔

Tracks via https://github.com/swc-project/swc/issues/5480

We do read issues, it may takes time to respond or we may do internal discussions. This seems overlap slightly between https://github.com/swc-project/swc/issues/4122 while technically not exactly same. Do you suggest...

It may need some more thoughts, but I'm under impression we (swc/core) eventually get rid of custom resolving behavior including existing options but instead let userland plugin / module does...

> Is this intended to support the case where e.g. I have a custom plugin which I want to run after transform of JSX to JS? No. This'll allow some...

> custom plugin can call an SWC transform pass itself (e.g. JSX to JS) before running it's own custom visitor? Yes, that's correct. But again, this doesn't mean anything aronud...

> I changed this so it is now OK for the user to provide, I'd like to request to take out these changes, for 2 reasons: - First, this does...

Sourcemapping is correctly working, while difference is how tsc picks up the mapping for the name vs. swc does. For both, see the actual stack frame points **swc-jest-stack-frame-name\src\test.ts:4:16** ``` //ts-jest...

Though, one thing to consider is in native stack at v8 it seems to pick up fn name correctly. ``` Error: irrelevant at Timeout. (/Users/ojkwon/github/swc/test.js:11:9) at Timeout.namedHandlerFn [as _onTimeout] (/Users/ojkwon/github/swc/test.js:4:10)...

yes, I think it makes sense swc* exposes a feature to let user controls. But name should not include anything 'wasmer'.