How to Diagnose vite: not found After npm ci in a Container Build
I recently worked on a project where a Node.js application used Vite to compile its frontend. It worked in a browser-hosted development environment, but its image build failed after the move to Azure Container Registry. The build reported a missing Vite executable after an earlier dependency install had failed. The container build ended with a simple error: sh: 1: vite: not found Vite already appeared in devDependencies . The build stage had run npm ci before calling the build script....
I recently worked on a project where a Node.js application used Vite to compile its frontend. It worked in a browser-hosted development environment, but its image build failed after the move to Azure Container Registry. The build reported a missing Vite executable after an earlier dependency install had failed. The container build ended with a simple error: sh: 1: vite: not found Vite already appeared in devDependencies . The build stage had run npm ci before calling the build script....