Angular Studio: The Missing Piece
Recently, Angular has undergone several excellent changes. People are calling it the Angular Renaissance and other things like that. And for no small reason — some of the changes really improve the average developer’s workflow. I wrote about these improvements here.
The things that I am enjoying about Angular 17 are the Control Flow Syntax, Signals (added in v16), and easily deferring content loads based on a set of conditions. It’s a real quality-of-life improvement to Angular.
But, despite how excellent these updates have been, Angular’s developer experience still leaves something to be desired. Despite being released in 2016, Angular still doesn’t have a proper IDE to use.
Maybe you take a pause, furrow your brow, and think “Wait, does he not know about Visual Studio Code? That’s kind of the standard”. You’re right, Angular does enjoy first-party support in VS Code, but VS Code is not an IDE. It’s a text editor with a bunch of extensions but lacks the advanced features normally found within an IDE. There are good things about this (like it being fairly fast to use), but it lacks several obvious features that people expect to find in IDEs. Even simple tasks like tearing off windows to form new windows don’t work, despite being on the backlog for years.
The Angular team develops the Angular Language Service, which means that all the new hotness added in Angular 17 is…
