Enable support for modern package managers (Yarn or PNPM) in the Frontend Deployment Pipeline of Cloud Manager

LyleSt1 · 2023-03-15T19:22:32+00:00

Request for Feature Enhancement (RFE) Summary: lease enable support for modern package managers in the Frontend Deployment Pipeline. Currently the pipeline only supports NPM, which although widely adopted is also generally known as the slowest solution for package management within the nodejs ecosystem. Consider support for yarn or pnpm, both of which outperform NPM from a CI/CD perspective. Use-case: We currently use Yarn on Managed Services to deploy full stack code. However, when migrating to Cloud Services and wanting to take advantage of the Front End (FED) pipeline, NPM is assumed and only the version can be altered via pipeline variables. We use Yarn as it has additional features and builds/deploys faster than NPM. Similarly, pnmp and Yarn PnP deploy about twice as fast as npm in our benchmark tests. Current/Experienced Behavior: Customers must use NPM and package-lock.json as the deployment package manager Improved/Expected Behavior: Customers can customize the FED deployment pipline to usee the package manager of their choice. This could be either an explicit selection, a pipeline variable, or the pipeline could lockfile detection (npm uses package-lock.json, yarn uses yarn.lock, pnpm uses pnpm-lock.yaml) Environment Details (AEM version/service pack, any other specifics if applicable): This request is for AEM Cloud Service, current version. Customer-name/Organization name: Toyota Motors North America (TMNA) Screenshot (if applicable) Code package (if applicable):

Forum|Forum|2 years ago
March 15, 2023
5 replies
1572 views

Request for Feature Enhancement (RFE) Summary:	lease enable support for modern package managers in the Frontend Deployment Pipeline. Currently the pipeline only supports NPM, which although widely adopted is also generally known as the slowest solution for package management within the nodejs ecosystem. Consider support for yarn or pnpm, both of which outperform NPM from a CI/CD perspective.
Use-case:	We currently use Yarn on Managed Services to deploy full stack code. However, when migrating to Cloud Services and wanting to take advantage of the Front End (FED) pipeline, NPM is assumed and only the version can be altered via pipeline variables. We use Yarn as it has additional features and builds/deploys faster than NPM. Similarly, pnmp and Yarn PnP deploy about twice as fast as npm in our benchmark tests.
Current/Experienced Behavior:	Customers must use NPM and package-lock.json as the deployment package manager
Improved/Expected Behavior:	Customers can customize the FED deployment pipline to usee the package manager of their choice. This could be either an explicit selection, a pipeline variable, or the pipeline could lockfile detection (npm uses package-lock.json, yarn uses yarn.lock, pnpm uses pnpm-lock.yaml)
Environment Details (AEM version/service pack, any other specifics if applicable):	This request is for AEM Cloud Service, current version.
Customer-name/Organization name:	Toyota Motors North America (TMNA)
Screenshot (if applicable)
Code package (if applicable):

V

vivekanand-mish

Adobe Employee

@lylest1 Looks good. Just one correction in your description "only the version can be altered via pipeline variables."- you can update node/ npm version from POM.xml as well - [0]. Also explore this- [1] and try to change execution goal to run yarn install.

<execution>
    <id>yarn install</id>
    <goals>
        <goal>yarn</goal>
    </goals>
    <configuration>
         <!-- optional: The default argument is actually
         "install", so unless you need to run some other yarn command,
         you can remove this whole <configuration> section.
         -->
        <arguments>install</arguments>
    </configuration>
</execution>

[0]- https://github.com/schoudry/eaem-extensions/blob/master/eaem-cloud-service/eaem-cs-spa-read-post-data/pom.xml#L117

[1]- https://github.com/eirslett/frontend-maven-plugin

F

FrankTran1

@vivekanand-mish,

That only works for the full stack pipeline. In the FED pipeline, we have no options to modify what toolchain is used to build the artifacts.

kautuk_sahni

Community Manager

@lylest1

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-12884. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

Kautuk Sahni

R

RohitKa1

Hi @kautuk_sahni ,

Could you please provide update on this feature request?

F

FrankTran1

Can we can an update on this feature?