[BUG] `npm ci` not working after successful `npm install`

[jakehockey10]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

When I run npm install I successful install my project's dependencies. When I run npm ci afterwards, I get an error:

$ npm ci
npm error code EBADPLATFORM
npm error notsup Unsupported platform for sass-embedded-all-unknown@1.93.3: wanted {"cpu":"!arm,!arm64,!riscv64,!x64"} (current: {"cpu":"x64"})
npm error notsup Valid cpu:  !arm,!arm64,!riscv64,!x64
npm error notsup Actual cpu: x64
npm error A complete log of this run can be found in: /home/jake/.npm/_logs/2025-11-25T00_29_19_394Z-debug-0.log

I initially thought this was an issue with sass-embedded, but I've since learned that this is likely a bug with npm itself: sass/embedded-host-node#404

I would like to continue using npm ci in my ci pipelines if that is still the suggested method (which makes sense to me based on recent descriptions I've received), but until this is resolved, I will need to use npm install directly with my CI pipelines. I'm not sure why the optional dependency is not treated as such when using the npm ci command.

Expected Behavior

Running npm ci after a successful npm install should not error out.

Steps To Reproduce

No response

Environment

• npm:
• Node.js:
• OS Name:
• System Model Name:
• npm config:

; copy and paste output from `npm config ls` here

[jakehockey10]

This issue is resolved by downgrading npm to 10 instead of 11.

[MRagunandhan24]

@jakehockey10 , can you try replicating this problem on the latest version of npm? (ie. npm i -g npm). If you find that the issue is reoccurring please provide more details such as package.json, npm config and steps to reproduce.