OJ Kwon

This is technically considered as breaking change, which should aim v2 major breaking for @swc/core if that's the case.

We do not have release branches for v2 yet. In short, this PR cannot go to current `main` branch.

would you able to uninstall `swc_cli` from cargo, then use `npx swcx` with `@swc/core` instead? it's prepared for those purpose as you said conflicting cli binary name can cause some...

yes, swcx and swc_cli is identical binary, just difference of distrubition - prior for the env doesn't have node / npm.

I'm removing this from bug but put into enhancement, this is mostly due to current situation where we have @swc/cli and experiemental swcx both. We'll likely need to realign once...

@alexeagle it sounds like a different issue, as bazel shouldn't rely on any global path resolution. Am I missing something? So the issue is swcx (native rust cli) doesn't work...

ref: https://github.com/rkyv/rkyv/issues/291

Latest swc_core / swc@core applied workaround this by disabling bytecheck for now. I'll close this, and track re-enabling via #5472.

Interesting thing is it shows different failure than original issue. ``` RangeError: Maximum call stack size exceeded at swc_ecma_parser::lexer::state::::next::{{closure}}::h33d6f7aea7ae9423 (wasm:/wasm/17487d42:1:9174010) at swc_ecma_parser::lexer::state::::next::h07de51b652b79274 (wasm:/wasm/17487d42:1:18208348) at swc_ecma_parser::parser::input::Buffer::bump_inner::{{closure}}::h947975deb7378d5c (wasm:/wasm/17487d42:1:67380653) at core::option::Option::or_else::hb735b09add21ca84 (wasm:/wasm/17487d42:1:30757873) at...

I don't have good explanations. Fyi, @swc/core works fine.