Error: spawn e:<folder><app>\scripts\test ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! Test failed. See above for more details.
I can run both the commands in the script file without scripty.
I don't have rollup running my production builds (I use webpack), so I don't really need the if statement in the script.
Am I right in thinking youβre running on Windows? I took a look through the scripty Windows instructions but Iβm not sure any of it applies to your situation, other than ensuring the file is in fact executable.
What happens if you run scripts/test directly from the command line?
Other than that Iβm not sure what to suggest. If you can get a minimal reproduction onto GitHub/GitLab/etc I can take a look.
I get this error when running "npm test".
Executing "e:<folder><app>\scripts\test":
events.js:174
throw er; // Unhandled 'error' event
^
Error: spawn e:<folder><app>\scripts\test ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! Test failed. See above for more details.
I can run both the commands in the script file without scripty.
I don't have rollup running my production builds (I use webpack), so I don't really need the if statement in the script.
Any suggestions?
Am I right in thinking youβre running on Windows? I took a look through the scripty Windows instructions but Iβm not sure any of it applies to your situation, other than ensuring the file is in fact executable.
What happens if you run
scripts/test
directly from the command line?Other than that Iβm not sure what to suggest. If you can get a minimal reproduction onto GitHub/GitLab/etc I can take a look.
I have this exact same issue. I cloned your repo to test if I did anything wrong, but I have the same issue with your code :/
I wonder if package updates have broken something. Iβll find some time later today to take a look at this again.
Thank you so much!
Are there any updates on this?