Pangular Inspector brings source scans and live inspection to Angular devtools. Alex Rickabaugh’s ViteConf talk, “Angular Compilation Past & Future,” covers Angular’s compiler history and its Rust/Oxc work. Also in brief: Julian Jandl’s production SSR recording.
Pangular Inspector
Devframe is a framework for writing devtools, already used by several tools outside Angular. It was created by Anthony Fu, the creator of Vitest and Slidev, and a core team member of Vue.js, Vite, and Nuxt.
Anthony announced Devframe in September 2026.
Pluggable, Extensible, and Playful DevTools | Devframe
Introduction to Devframe, a framework for building pluggable, extensible, and playful DevTools.
devfra.me
Now, Angular has a new tool built on it: Pangular Inspector, maintained by Erkam Yaman and Santosh Yadav.
Santosh has been around the Angular community for quite some time. He is a GitHub Star, Nx Champion, and Google Developer Expert.
Erkam maintains the Turkish translation of the Angular documentation and has recently contributed extensively to Angular Native - which we covered last episode - including its integration with Analog’s file-based routing.
Pangular aims to become the unified devtools for Angular. Built on Devframe, it can scan the source code of an Angular app and inspect its live state.
It shows components, signals, NgRx stores, services, forms, and routes. Source scans tell you what is declared in your project; live inspection shows the instances and values in the running application.
That information is available through its inspector panel and to your coding agent through MCP.
Pangular Inspector | The unified Angular devtools
Inspect Angular components, signals, dependency injection, routes, forms and stores. In the page, from the CLI, or through a coding agent over MCP.
pangular-inspector.dev
Erkam’s Analog integration for Angular Native
Angular Compilation Past & Future
Alex Rickabaugh also spoke at the online ViteConf. His talk, “Angular Compilation Past & Future,” starts with Angular’s compilation history before moving into the current work involving Rust and Oxc, which we discussed last episode as well.
Alex described splitting Angular’s compiler into two parts. The expensive analysis would move to a native implementation written in Rust, while code generation would remain in Node.js.
The choice of Rust is closely tied to Oxc, VoidZero’s JavaScript toolchain. Alex points to its adoption across modern JavaScript tools, including Vite, as a reason to build on it for the long term.
Compilation would still start with a tsconfig. The Oxc-based Angular analyzer would extract metadata and pass it to the Node.js code generator, which he calls the preprocessor. That would produce either TypeScript with runtime code or a different file containing code for type checking and the language service.
The following link includes a timestamp that takes you straight to Alex’s talk.
Production SSR with Julian Jandl
And the recording of Julian Jandl’s talk on SSR is now available. He presents the work he and his colleagues did on a betting platform, the challenges they encountered, and their solutions using custom strategies for Incremental Static Regeneration, or ISR.
Upcoming conferences
NG Poland - 17 November 2026, Warsaw.
angularday - 20 November 2026, Verona.
Aingular TLV - 7 December 2026, Tel Aviv.
NG Switzerland - 11-12 February 2027, Lucerne area.
NG Baguette - 28 May 2027, Paris.
Top comments (0)