Qingyu Wang
Qingyu Wang
To be honest, I don't quite remember. Maybe it is from cs143 2020? Since I created this repo at 2020.
Using the workspace version(4.9.4) works for me!
Thanks! It is fixed. Also, the documentation PR link is updated.
> I think that makes sense to add also `react-native` target for Hermes bundled with React Native. `core-js-compat` and `compat-table` also have data for this. I agree with adding `react-native`....
Seems like this issue exists when TS namespace alias(`import alias = Namespace`) is implemented. https://github.com/babel/babel/pull/13528/files#diff-17aa1d2f85bafbf2a6002e7d4587af251ebe0b102da595ce88f294b1f4adecd4R4 I would like to take a look on this one in the next few days.
A SWC plugin has been implemented at https://github.com/swc-project/plugins/pull/326
I think it makes sense to use `JsStatsError[]` for `compilation.errors`. ```diff class Compilation { - get errors(): any; + get errors(): JsStatsError[]; get warnings(): JsStatsWarning[]; } ``` cc @coder-xiaotian @h-a-n-a
Sure! I'm glad to send a PR. But actually, I'm not 100% sure about the correctness. Since it will make the compilation unstable(depends on the order of the requests).
Any progress on this? If the resolver cannot resolve wildcard correctly for now, can we iterate over `exports` in Rsbuild and set alias using manually resolve (with correct `conditionName`)?
@microsoft-github-policy-service agree