[ 
https://issues.apache.org/jira/browse/YARN-11875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shilun Fan resolved YARN-11875.
-------------------------------
    Fix Version/s: 3.5.0
                   3.4.3
     Hadoop Flags: Reviewed
       Resolution: Fixed

> Fix build failure caused by [email protected]
> ---------------------------------------
>
>                 Key: YARN-11875
>                 URL: https://issues.apache.org/jira/browse/YARN-11875
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: buid
>    Affects Versions: 3.5.0, 3.4.3
>            Reporter: Shilun Fan
>            Assignee: Shilun Fan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.5.0, 3.4.3
>
>
> A build failure occurs in the Yarn UI module due to an incompatible 
> dependency version of {{{}[email protected]{}}}, which requires Node.js ≥ 18.
> The current build environment uses Node.js 12.22.1, resulting in the 
> following error during dependency installation
> {code:java}
> error [email protected]: The engine "node" is incompatible with this module. 
> Expected version ">=18". Got "12.22.1"
> error Found incompatible module. {code}
> h3. *Root Cause*
> The {{color}} package was pulled in as a transitive dependency from other 
> modules (e.g., {{{}apidoc{}}}).
> Version {{5.0.2}} introduced a strict Node.js engine requirement (≥18), which 
> is incompatible with the current Node 12 environment.
> h3. *Fix*
> Manually pinned the dependency to a Node 12–compatible version:
> "resolutions": \{
>   "color": "^3.1.3"
> }
>  
> This resolves the build failure without requiring a Node.js upgrade.
> h3. *Verification*
>  * The Yarn UI build completes successfully under Node.js 12.22.1.
>  * No runtime or API compatibility issues were observed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to