Boshen
Boshen
> experimental decorators and useDefineForClassFields: false is not support by oxc From rolldown-vite integration.
> @Boshen @Dunqing do you have guys any kind of ETA? What are you using oxc for that requires decorators, and which version of decorators do you need?
The team has agreed to implement typescript `--experimentalDecorators` first, which is simpler and what most people use today. Research this week, implementation will probably start next weerk.
Legacy decorator has been implemented and is being integrated into Rolldown. A `decorator?: DecoratorOptions` option has been added to the `oxc-transform` package. Stage 3 ecma decorators is tracked in *...
# Research ## builder pattern https://github.com/colin-kiegel/rust-derive-builder ## `with` pattern https://docs.rs/schemars/latest/schemars/gen/struct.SchemaSettings.html#method.with ```rust pub fn with(self, configure_fn: impl FnOnce(&mut Self)) -> Self ``` ``` use schemars::gen::{SchemaGenerator, SchemaSettings}; let settings = SchemaSettings::default().with(|s| {...
## Proposal What am looking for is consistency and future compatibility. ```rust // Some tools return `Result`, some tools return recoverable errors. // `OxcDiagnostic` can also contain warnings. // When...
Oh yes, I forgot to mention another goal is to enable `cargo-semver-checks` after v1.0.0.
We currently have an [`oxc`](https://docs.rs/oxc/0.24.2/oxc/) crate for unifying all the sub-crates. I plan to expose a `Compiler` API similar to `rustc_driver` and `rustc_interface`. The [rustc API](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_driver/struct.RunCompiler.html) uses callbacks, closures and...
I decided to not include any builder patterns in the public APIs, they are super confusing for new comers from JavaScript, who are used to passing objects with spread `{...
It seems like we need a `TransformerFactory` for storing options, otherwise we'll be repeatedly initializing the options. But ... I'll just add `define` and `inject` options to `TransformOptions` to get...