Repository navigation
disconnect and throw this error each time #484
Description
Error: spawn npm ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn npm',
path: 'npm',
spawnargs: [ 'install', '--include=dev' ]
}
node:internal/process/promises:391
triggerUncaughtException(err, true /* fromPromise */);
^
Error: spawn npm ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn npm',
path: 'npm',
spawnargs: [ 'install', '--include=dev' ]
}
Activity
aakash-a-dev commentedon Feb 13, 2025
I believe you're using Windows
mosi-sol commentedon Mar 10, 2025
I believe Windows is terrible, but some users have the same problem. Is there a solution for them? Like wsl!
aakash-a-dev commentedon Mar 10, 2025
Yes in wsl it works
mosi-sol commentedon Mar 12, 2025
@aakash-a-dev
I'm trying on a Windows system (for test this issue) and tried running the app with WSL. However, after launching the app and installing dependencies "within" it, the application crashes. It seems that WSL isn't a viable solution for Windows users in this case.
Any insights or alternative suggestions would be appreciated.
Thanks!
aakash-a-dev commentedon Mar 12, 2025
@mosi-sol I have a PR raised already on this which helping me to run the app in my windows system. Although it's not tested yet but you can try this branch for now
#466
PS: Will like your feedback on this PR. TIA
mosi-sol commentedon Mar 13, 2025
@aakash-a-dev that's failed. thanks for share.
aakash-a-dev commentedon Mar 13, 2025
Um failed as in?
mosi-sol commentedon Mar 13, 2025
@aakash-a-dev hey, not stable yet. i have linux, but like to know why windows have problem with srcbook.
And thanks for u r job 💐