Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Is there any repo that is up to date for using React with AEM?

Avatar

Level 2

Hello, 

I am littered with errors and deprecated packages when using the WKND SPA repo and following the Adobe's documentation to implement an SPA. There are always issues either in the ui.frontend with package version collisions or packages in Maven that are not resolving. Are there any reliable resources to implement an up to dat SPA in AEM or are we stuck with deprecated packages and packages not resolving in the frontend? Any tutorials or repos with clean code and working packages would be greatly appreciated. 

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

The one I tested on my local latest(as of today) AEMaaCS SDK is "React - WKND SPA 1.0.3"[1]. You may fetch it as follows :

 

$ git clone git@github.com:adobe/aem-guides-wknd-spa.git
$ cd aem-guides-wknd-spa
$ git checkout React/latest
$ mvn clean install -PautoInstallSinglePackage

If we follow along with the tutorials on https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/s... one may likely make a mistake. Don't hesitate to validate and check out the final latest working solution[1]. For deprecated packages/vulnerabilities, fix them with npm audit[2]. In case of any issues, feel free to log a ticket.

 

[1] https://github.com/adobe/aem-guides-wknd-spa/releases

[2] https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities

View solution in original post

1 Reply

Avatar

Correct answer by
Employee Advisor

The one I tested on my local latest(as of today) AEMaaCS SDK is "React - WKND SPA 1.0.3"[1]. You may fetch it as follows :

 

$ git clone git@github.com:adobe/aem-guides-wknd-spa.git
$ cd aem-guides-wknd-spa
$ git checkout React/latest
$ mvn clean install -PautoInstallSinglePackage

If we follow along with the tutorials on https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/s... one may likely make a mistake. Don't hesitate to validate and check out the final latest working solution[1]. For deprecated packages/vulnerabilities, fix them with npm audit[2]. In case of any issues, feel free to log a ticket.

 

[1] https://github.com/adobe/aem-guides-wknd-spa/releases

[2] https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities