Pain point · Self-hosting & upgrades · Blocks work
Installing community nodes fails with spawn npm ENOENT on Windows
1 source thread · first seen 2025-12
Summary
After an update, installing community nodes on Windows fails because npm is not resolved correctly. The reporter patches the compiled service file as a fix.
- Affects
- Windows users
- Workaround
- Patch community-packages.service.js to add shell: true to the npm execFile calls.
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“When installing community nodes in n8n under the Windows environment, the "spawn npm ENOENT" error often occurs”