How to add npm install --progress=false --force in clouldflare page code deploy?

I have an angular project and planing to switch to pages from aws s3. I want to run --force instead of npm install --progress=false. Please help.

2023-10-23T10:25:10.69542Z    Cloning repository...
2023-10-23T10:25:12.467452Z    From
2023-10-23T10:25:12.468022Z     * branch            bdaa4e67f2d52c8a73e932d6d75dd3bb43c710b0 -> FETCH_HEAD
2023-10-23T10:25:12.70585Z    HEAD is now at bdaa4e6 npm i --force
2023-10-23T10:25:12.837488Z    Success: Finished cloning repository files
2023-10-23T10:25:13.574409Z    Detected the following tools from environment: [email protected], [email protected]
2023-10-23T10:25:13.575842Z    Installing project dependencies: npm install --progress=false
2023-10-23T10:25:15.626213Z    npm ERR! code ERESOLVE
2023-10-23T10:25:15.629099Z    npm ERR! ERESOLVE unable to resolve dependency tree
2023-10-23T10:25:15.629373Z    npm ERR! 
2023-10-23T10:25:15.629591Z    npm ERR! While resolving: [email protected]
2023-10-23T10:25:15.629736Z    npm ERR! Found: @angular/[email protected]
2023-10-23T10:25:15.629836Z    npm ERR! node_modules/@angular/common
2023-10-23T10:25:15.629941Z    npm ERR!   @angular/common@"^14.3.0" from the root project
2023-10-23T10:25:15.630047Z    npm ERR! 
2023-10-23T10:25:15.630162Z    npm ERR! Could not resolve dependency:
2023-10-23T10:25:15.630297Z    npm ERR! peer @angular/common@"^12.0.0 || ^13.0.0-0" from @angular/[email protected]
2023-10-23T10:25:15.630403Z    npm ERR! node_modules/@angular/cdk
2023-10-23T10:25:15.630501Z    npm ERR!   @angular/cdk@"^12.2.9" from the root project
2023-10-23T10:25:15.630602Z    npm ERR! 
2023-10-23T10:25:15.630704Z    npm ERR! Fix the upstream dependency conflict, or retry
2023-10-23T10:25:15.630804Z    npm ERR! this command with --force or --legacy-peer-deps

Adding npm install --force in npm run build not helping!!

The pipeline by defaults add:

Installing project dependencies: npm install --progress=false

Which is a problem for me

I’ve successfully resolved the issue and I’m sharing this solution to assist fellow developers!

As I couldn’t find a direct method to execute ‘npm i --force’ within Cloudflare Pages, I was able to make it work by leveraging the ‘GitHub - cloudflare/pages-action’ GitHub action.

I initially attempted an alternative solution using ‘Deploy to Cloudflare Workers with Wrangler · Actions · GitHub Marketplace · GitHub’, but unfortunately, it didn’t yield the desired results.


This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.