Post

VoidZero
@voidzero.dev

Introducing the Oxc Angular Compiler ✨ ◆ 6.4x faster than Angular CLI ◆ 20.7x faster than Webpack ◆ First-class @vite.dev plugin with full HMR ◆ Built with Oxc ◆ Not another slop fork While this is experiment, the @angular.dev team is looking into an Oxc integration. voidzero.dev/posts/oxc-an...

voidzero.devHow we made the Angular Compiler faster using AIHow VoidZero built the Oxc Angular Compiler, an AI-powered Angular compiler that achieves up to 20x faster code compiling speed.

10 reposts67 likes

Nicolas Dubien
@nicolas.dubien.me

Very cool reading. I was recently looking for such a story explaining how to leverage AI on massive rewrites like this one. I'm still unclear about the review side. How much did you review the produce code? Is it needed given tests are ok? (Honest questions without preferred answer, really curious)

Passle ☭
@passle.dev

For @custom-elements-manifest/analyzer I also avoided using the ts checker because it significantly slows things down, and instead just used ts for parsing and then ast analysis. One of the down sides of that though is not having accurate scope/variable tracking and type information ...

Passle ☭
@passle.dev

How did you solve that with oxc? Also, the blog does read quite similar to the vinext thing, which many people seemingly regarded a "slop fork", what exactly makes this not a slop fork? (Note: im not saying it is a slop fork, im just curious how you distinguish between what is and isnt)