Solved Deploy npm install aşamasında hata

[tailadmin]

Vartsayılan olarak güncelleme ile seçili 26 sürümünde bu hata oluştu, Node.js->Versiyonlar altından farklı bir sürümü seçip tekrar 26 seçince düzeldi. Fakat bu geçişi yapana kadar build alınamadı. Geçişten sonra sorunsuz build tamamlandı.


=== Pipeline: Build ===
Started: 2026-08-19T13:26:20Z

--- Step 1: Bağılılıklar (shell) ---
npm error code MODULE_NOT_FOUND
npm error Cannot find module './cache/policy.js'
npm error Require stack:
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/make-fetch-happen/lib/fetch.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/make-fetch-happen/lib/index.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/index.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/pacote/lib/remote.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/pacote/lib/git.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/pacote/lib/fetcher.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/pacote/lib/index.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/@npmcli/metavuln-calculator/lib/index.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/audit-report.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/index.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/index.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/node_modules/libnpmfund/lib/index.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/lib/utils/reify-output.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/lib/utils/reify-finish.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/lib/commands/ci.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/lib/npm.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/lib/cli/entry.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/lib/cli.js
npm error - /opt/panelica/services/nodejs/26/lib/node_modules/npm/bin/npm-cli.js
npm error A complete log of this run can be found in: /home/tailadmin/.cache/npm/_logs/2026-08-19T13_26_20_831Z-debug-0.log

 

[admin]

Thanks for the detailed report, and especially for including the full npm error and the log stack. That made this quick to pin down.

You were not doing anything wrong, and it was not your project dependencies. The failure was on our side: the Node.js 26 runtime that shipped was missing one internal file that npm itself needs (part of npm own "make-fetch-happen" module, .../lib/cache/policy.js). With that file absent, npm could not start at all, so any "npm install" / "npm ci" for any package failed before it ever looked at your code. That is also exactly why switching to another version and back fixed it: selecting/installing a version triggers a fresh download, and a complete copy of the runtime replaced the incomplete one.

We traced the root cause to our packaging step, which was too aggressively stripping folders named "cache" and accidentally removed npm own source folder of the same name. Two fixes were made:

1. The panel now verifies a runtime is actually usable (that npm really loads), not just that the "node" binary exists. If a runtime is found incomplete, the panel repairs it automatically on startup and again right before a deploy step, instead of failing with a cryptic MODULE_NOT_FOUND. This is rolling out as a panel update; existing servers self-heal once it is applied.
2. The packaging bug itself is fixed, so runtimes are shipped complete going forward.

If you run into it again before the update reaches your server, the quick manual fix is: Node.js -> Versions -> remove the affected version, then install it again (that re-downloads a complete copy).

Thanks again for reporting it. It turned out to be a genuine bug, and your logs are what made it findable.