When using the ui.frontend project, why are clientlib-dependencies and clientlib-sites ignored in Git. Don't these folders and the code within them need to be part of version control?
Solved! Go to Solution.
Views
Replies
Total Likes
@JonMaguire
As per my understanding these clientlibs are created when code is built and deployed and it's content mostly varies on build.
It's something like Node Modules in react which is never committed in GIT and is a part of build of build process.
So, if this is the case I think there is any need to commit it as part of the code in Git.
Thanks,
Nikhil
@JonMaguire
As per my understanding these clientlibs are created when code is built and deployed and it's content mostly varies on build.
It's something like Node Modules in react which is never committed in GIT and is a part of build of build process.
So, if this is the case I think there is any need to commit it as part of the code in Git.
Thanks,
Nikhil
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Thanks, but my app is not React. I understand being able to add clientlibs as dependencies to templates. My team wants to be able to see the generated css in a human-readable format. For instance site.css within clientlib-site.
Views
Replies
Total Likes
Views
Replies
Total Likes
@JonMaguire
Refer the below link of latest archetype where the clientlibs clientlib-dependencies and clientlib-site inside ui.frontend.general in clientlib.config.js file.
If you don't have ui.frontend.general then look inside ui.frontend.
https://github.com/adobe/aem-project-archetype/blob/master/src/main/archetype/ui.frontend.general/cl...
I am not sure we can customize it's functionality or not.
Hope this helps!!
Thanks,
Nikhil
Views
Likes
Replies
Views
Likes
Replies