Google I/O 2023’s flagship event happened last month, and Angular had a ton of fun announcing Angular v16! Read on to learn more about everything Angular announced at I/O this year. What’s new in Angular https://medium.com/media/b5904d28da142e18ff0261e275729388/href Minko and Madleina share about the latest from Angular, including updates on hydration, SSR, and reactivity. Discover everything from community updates and the request for comments process to new features landing in v16 and beyond! Rethinking Reactivity with Signals https://medium.com/media/928a5bf8d15a9e9e ..read more

The Angular team is evidence driven — we collect feedback from developers to decide what should be part of our roadmap. We get data from dozens of sources such as conversations with people, comments on social media, surveys, market research, and much more. One of the main sources which helps us make informed decisions is our annual developer survey. In 2022 we increased the number of questions which helped us get a more comprehensive look into the opportunities for Angular. We’re grateful to all the over 12k developers who shared their feedback with us! In the section below, you’ll learn more ..read more

Six months ago, we reached a significant milestone in Angular’s simplicity and developer experience by graduating the standalone APIs from developer preview. Today, we’re thrilled to share that we’re continuing the Angular Momentum with the biggest release since the initial rollout of Angular; making large leaps in reactivity, server-side rendering, and tooling. All this comes with dozens of quality-of-life improvements across feature requests, with over 2,500 combined thumbs up on GitHub! Angular v16 release This post includes lots of content, capturing most of the improvements we m ..read more

Angular water bottle In May of 2022, we shared Angular’s vision for the future, where we committed to investing in server side rendering and hydration. Angular has had support for server side rendering through Angular Universal, which originally came into being thanks to third party contributors. Eventually Angular Universal became the official SSR library for Angular. Fast forward to 2023, and SSR is now an essential part of modern web applications and has been for a few years. We’ve conducted surveys and the community has let us know that server side rendering is the top area Angul ..read more

Andrew Scott’s pup gazing at the Oregon CoastPrior advice Conventional wisdom might suggest that test authors should stub external dependencies like ActivatedRoute or RouterLink and spy on services and service methods like navigateByUrl. A defense for this testing strategy might be “Relying on the real router would make them brittle. They could fail for reasons unrelated to the component.” This isn’t entirely true, but for now we will point out one very important detail in this defense that’s often ignored. Per the documentation: “A different battery of tests can explore whether the ..read more

Over the past year we removed Angular’s legacy compiler and rendering pipeline which enabled the development of a series of developer experience improvements in the past couple of months. Angular v15 is the culmination of this with dozens of refinements which lead to better developer experience and performance. Sunrise photo by Minko GechevStandalone APIs are now stable! In v14 we introduced new standalone APIs which enable developers to build applications without using NgModules. We’re happy to share that these APIs graduated from developer preview and are now part of the stable API ..read more

Photo by Ylanite Koppens The Angular team has been busy making some meaningful updates to the Angular router that are available as of Angular v14.2. We’re pleased to share some recent improvements. Read on to learn more. New Router API for standalone We’ve introduced a way to use the Router without the need for RouterModule and improved tree shaking for reduced bundle sizes. First, let’s focus on the new router integration API. Here’s how to use the router without a RouterModule. In the bootstrapApplication function, we provide the router configuration to the providers array using th ..read more

Photo by Diego PH on Unsplash In the Angular v12 release blog post we announced plans to investigate the future of Protractor. Based on community feedback via the RFC process, we’ve decided to deprecate Protractor, while working with the community to find a long term support option for active projects that wish to continue using Protractor. The e2e testing experience In Angular v12, we added support for three popular e2e testing frameworks, Cypress, Nightwatch, and WebdriverIO. Playwright also has a migration guide. Currently, new projects running `ng e2e` will walk developers through cho ..read more

photo by Emma Twersky We are excited to announce the release of Angular v14! From typed forms and standalone components to new primitives in the Angular CDK (component dev kit), we’re excited to share how each feature makes Angular more powerful. Since our last release, we completed two major requests for comments (RFC), which provided an opportunity for the entire Angular community to provide design feedback on proposed changes. As a result, our Strictly Typed Reactive Forms RFC closed our #1 GitHub issue, and our Standalone APIs RFC introduced a simpler way to author Angular apps ..read more

Photo by Pixabay In the Angular 2021 recap and 2022 preview post, we shared our plans for 2022. As we are almost midway through 2022, this is a great time to give more insights into our long-term plan and some hints of what we might work on in 2023. Improving and simplifying the developer experience is a major theme we started to work on in 2022 and will continue into 2023 and beyond. We are excited to see the first step launch in v14 with Standalone components in developer preview. This is only the start in rethinking the developer journey and experience, with an emphasis on the ini ..read more