Last year today I decided to work on Oxc persistently everyday. I reached the goal today.
What I can't tell from the graph is when I got:
* Married
* Went to Australia for honeymoon
* Left ByteDance (Rspack)
* Joined @voidzerodev
We wrote a minifier, where it outperforms esbuild in terms of performance and compression size.
This minifier is being integrated into @rolldown_rs as its built-in minifier, and @rolldown_rs is set to become the future of @vite_js.
Misconfigured React useEffect dependency array DDOSing its own service, causing huge outage.
I'm interested in the usage pattern, will a type-aware linter rule mitigate this?
If you are bored and is looking for open source contributions, here is a cool trick:
Find a repo and run `npx oxlint@latest -D no-constant-binary-expression` and then fix the bugs 😅
Sorry for picking you as an example @getsentry🌹
oxlint + tsgolint = no slow down!
no-floating-promises completes 4.4k files in 3.2 seconds, in the vscode repo.
typescript-go is the future, all credits to the ts-go team! We just glued everything together 😀
github.com/microsoft/type…
With tsgo + isolated declarations, type checking will be fully parallelized.
Given tsgo can work on multiple threads, ID removes the need to walk the module graph for build order. It can check each file in isolation on different threads.
Enable isolated declarations today for