Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

env-cmd fails on WSL2

See original GitHub issue

env-cmd 9.0.3 env: Windows 10 WSL2

env-cmd -f ./.env.staging my-build-script                             
Error: spawn EPERM
    at ChildProcess.spawn (internal/child_process.js:394:11)                                                                at Object.spawn (child_process.js:535:9)                                                                                
at Object.spawn (/home/jdunlap/n/lib/node_modules/env-cmd/node_modules/cross-spawn/index.js:12:24)                      at Object.<anonymous> (/home/jdunlap/n/lib/node_modules/env-cmd/dist/env-cmd.js:57:30)                                  
at Generator.next (<anonymous>)
    at fulfilled (/home/jdunlap/n/lib/node_modules/env-cmd/dist/env-cmd.js:4:58) {                                        errno: 'EPERM',                                                                                                         
code: 'EPERM',                                                                                                          
syscall: 'spawn'                                                                                                      
}

Issue Analytics

State:
Created 4 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

jadboxcommented, Aug 12, 2019

Closing this for now as I don’t have time to set up the Windows env again to test. Hopefully there’s a better way to diagnose problematic wsl PATH issues in the future (if that’s the issue).

1reaction

jadboxcommented, Jul 27, 2019

I had to leave wsl2 due to the bug… I’ll give it another try over the weekend if I can with the ‘clean PATH’ trick. Anything else I should try?