Release Core Components JS as npm modules

[jkoebner]

For an improved integration of core components JS in an application that uses the core components, it would be very useful to have versioned NPM Modules of the Core Components' JS.

The @adobe namespace in npm could be used. The version of the components should be according to the core components release version. That would result, for example, in component names like:

@adobe/core/accordion/v1@2.13.4 @adobe/core/text/v1@2.13.4 @adobe/core/text/v2@2.13.4

This would be an easy step that helps a lot in integrating the components in modern FE build stacks.

The prerequisites for this are given because the js modules have a clean capsuled component scope. All the components would need is

• an .npmrc per js file
• an export default at the end of the js or a plugin that converts plain js into es6 modules
• an integration of this module release in the build job and finally in the build pipelines

[bpauli]

@jkoebner Thank you for submitting this enhancement request!

Maybe you can provide a PR which covers the conversion of the JS files into es6 modules as a first step?

[jkoebner]

@bpauli thank you for the feedback. i will try to provide the code in a way that integrates best with the repo and file structure and the component logic:

• Core Components Content Module receives a main entry point that exports all modules
• Components will receive a file that imports them and converts / exports as es6 modules
• Components can be selected from main js entry point

However, it would be important for me to know if it is possible to add an "npm publish" to the release pipeline. We can only make use of this feature if we can refer to the core components in our package.json and thus import them in the component js of the components that build up on the core components. Please let me know if you see any blockers for that.

[jkoebner]

To be more specific, the question refers to releasing the module defined in aem-core-wcm-components/content/package.json

[bpauli]

@jkoebner Thank you for reaching out. I don't see any blockers to add an npm publish to the release pipeline. Looking forward to your PR!

[jkoebner]

Hi @bpauli @vladbailescu - there was no update on the PR and no feedback. we would really love to have that feature and are able to contribute. Is there any feedback to the suggested solution - should we reiterate and update it? Having adobe core components as npm module would greatly improve flexibility for the frontends. BR and thank you for your feedback