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

Migrate ootb AEM React SPA to AEM React SPA with Vite instead of Webpack? Or upgrade Webpack 4 to Webpack 5

Avatar

Level 2

When we create AEM React SPA Archetype project (frontendModule="react") we get AEM SPA Editor JS SDK and the ootb React application (ui.frontend) based on the Create React App with core components with necessary mappings 

https://experienceleague.adobe.com/en/docs/experience-manager-learn/getting-started-with-aem-headles...

- Is there a definite guide on how to migrate AEMs ui.frontend CRA to React Vite application?

- Any documentation on how to get there with Vite Plugin (aemvite.dev)?

 

Additionally, is it possible to upgrade from Webpack 4 to Webpack 5 in the context of AEM ui.frontend?

 

Thanks

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

There are hints suggesting that, for example https://www.aemvite.dev/guide/backend/clientlibs/#add-esmodule-htl-binding . You won't use HTL if this would be an SPA project, among others.

 



Esteban Bustamante

View solution in original post

4 Replies

Avatar

Community Advisor

Hi, 

 

There is no official guide to migrate from SPA archetypes to Vite. Technically, I think it is possible; however, some things are pre-configured to run smoothly with Webpack. For example, the manifest.json that SPA relies on is set and easy to configure in Webpack, whereas in Vite, you need to do extra configuration, etc.

 

From what I can read, VitePlugin is a different story. This plugin is meant for swapping Webpack in the regular archetype, not the SPA one, and the steps are described on the same page you posted. Please check here: https://www.aemvite.dev/guide/front-end/ .

 

Hope this helps



Esteban Bustamante

Avatar

Level 2

Thanks for a quick insight -

I couldn't confirm this statement, from the aem vite plugin documentation - This plugin is meant for swapping Webpack in the regular archetype - Where does this come from?

 

Thanks again

Avatar

Correct answer by
Community Advisor

There are hints suggesting that, for example https://www.aemvite.dev/guide/backend/clientlibs/#add-esmodule-htl-binding . You won't use HTL if this would be an SPA project, among others.

 



Esteban Bustamante

Avatar

Administrator

@gangula2018 Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!



Kautuk Sahni