Skip to content

Best practice to merge Assets share commons implementation into existing AEMasACS custom repository #1286

@kdesineedi

Description

@kdesineedi

We have a regular AEM repo - customer git that sync with Adobe Git to deploy in AEMAsaCS and uses webpack5

We want to integrate the Assets share commons and create pages with a mix of custom components and Assets Share commons components

While including the dependency is straightforward the question is on the ui.frontend module - the "New project Setup guide" in the documentation does not specify how to integrate the assets share commons ui.frontend into an existing ui.frontend module

I am reaching out to understand if there is any guidance on this?

I am also running into a lot of version conflicts when I try to merge this as a separate assets share commons clientlib (Reference issue #1259 )(webpack 4 Vs webpack 5)

AEM SDK - Adobe Experience Manager 2024.9.17964.20240924T170544Z-240800

Assets share commons - 3.10.10

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions