Default Angular JS not available in AEM 6.3 publish instance

[rubenf42159101]

Hi,

We are migrating our project from AEM 6.1 to 6.3. We use AEM's default Angular JS (V 1.2.28) in our project. This Angular JS is not available in AEM 6.3 publish instance under /etc/clientlibs. But we could find the same Angular JS folder in AEM 6.1 author under /etc/clientlibs.

Why AEM hide or does not provide default Angular JS based on run mode? How to enable or make it available for AEM 6.3 publish?

Thanks and Regards,

Ruben Fernando

[rubenf42159101]

Hi,

We are migrating our project from AEM 6.1 to 6.3. We use AEM's default Angular JS (V 1.2.28) in our project. This Angular JS is not available in AEM 6.3 publish instance under /etc/clientlibs. But we could find the same Angular JS folder in AEM 6.1 author under /etc/clientlibs.

Why AEM hide or does not provide default Angular JS based on run mode? How to enable or make it available for AEM 6.3 publish?

Thanks and Regards,

Ruben Fernando

[Jörg_Hoh · Accepted solution]

I don't know about the reasons this clientlib was dropped from the product. But in the projects I worked we never relied on the clientlibs shipped with the product to build the frontend on. Mostly because these libraries were outdated and the frontend devs wanted to decide freely on the version they want to use.

And from what I know this was also the perception of the AEM developers. A clientlib shipped with AEM is used by the product itself; but for the purpose of the project developers to build a custom internet-facing frontend you should integrate your own copy of a JS framework of your choice.

That's the best explanation I can offer.

Jörg

[smacdonald2008]

You can always create a client lib and add these files to it.

See this community article --

Adobe Experience Manager Help | Integrating the AngularJS Framework into Adobe Experience Manager

For version 2 - see http://www.aemcq5tutorials.com/tutorials/integrate-aem-with-angular-2-js/

[Jörg_Hoh · Accepted solution]

I don't know about the reasons this clientlib was dropped from the product. But in the projects I worked we never relied on the clientlibs shipped with the product to build the frontend on. Mostly because these libraries were outdated and the frontend devs wanted to decide freely on the version they want to use.

And from what I know this was also the perception of the AEM developers. A clientlib shipped with AEM is used by the product itself; but for the purpose of the project developers to build a custom internet-facing frontend you should integrate your own copy of a JS framework of your choice.

That's the best explanation I can offer.

Jörg