Finding a Path Forward with AngularJs

February 1st, 2021

A road going through the English countryside
Photo by Illiya Vjestica on Unsplash

In January of 2018, we laid out our plans for the final releases of AngularJS before entering long-term support. Then in July 2020, we extended the LTS date to December 31st, 2021 due to the global pandemic.

We understand that teams using AngularJS in production may have questions about what options are available to them. Let’s take a look at a few of the alternatives.

Upgrade to Angular

Angular, the successor to AngularJS, uses many of the same philosophies. Angular continues to move forward increasing stability, developer productivity and forging a new path forward for the development of scalable applications for the web. As a best practice, we recommend that teams upgrade their applications to Angular.

The Angular team offers ngUpgrade, a library that lets you run Angular and AngularJS in the same application, allowing incremental migration. We defined best practices and a migration strategy for upgrading applications to Angular from AngularJS using ngUpgrade. Because applications vary in size and complexity the upgrade may require some flexibility. We also created a forum to collect best practices, and a migration tool to help analyze your application and make migration recommendations.

The upgrade guide gives detailed instructions on how to prepare your application for an upgrade and even includes code samples and examples. Head over to for more information.

You can find more resources like communities, courses, and more at

Continue with the latest version of AngularJS

If upgrading to Angular isn’t an option at this time, then you can continue to rely on AngularJS. We expect that AngularJS applications that work now will continue to work in the future. All published versions of AngularJS on npm and bower will continue to be available. The framework will receive updates that cover security issues and breaking browser bugs until December 31st, 2021. We don’t anticipate any changes being required by teams using AngularJS.

Be mindful that this could trigger alerts about the user of unsupported software.

If teams need long-term support after the December 31st, 2021 date this is another option to consider.

Extended Long Term Support

We know that many teams will need to continue to rely on AngularJS in the future and that some of them need to show that they only use supported software. Companies have SLAs of their own or have to meet regulatory/compliance needs around support. There is a solution if you require ongoing support.

The independent team at XLTS,dev offers extended long term support for AngularJS. Starting January 1st 2022 team will maintain a fork of the latest version of AngularJS and provide software updates that fit any of the following criteria:

  • Security Patches: A security flaw is detected in XLTS for AngularJS
  • Browser Breaking Changes: One of the major browsers releases a version that will cause current production applications using the XLTS for AngularJS to stop working
  • jQuery Patches: The jQuery library releases a version that will cause current production applications using XLTS for AngularJS to stop working

Find out more information over at

The path forward

AngularJS wouldn’t have been a success without you — the incredible community. We are thrilled about the future of Angular and are grateful for the lessons learned and road travelled with AngularJS. We will continue to build the future of the web with Angular and look forward to taking this journey with you.

The original post Finding a Path Forward with AngularJs.