Closed tad-lispy closed 6 years ago
Using DEBUG=*
from the debugging section does tell you when there is a problem like this.
I respectfully disagree with closing this one. Having a possibility to infer the reason of failure from logs doesn't satisfy the need for proper error handling (with try - catch
etc.).
When it comes to logs, IMHO this kind of failure should be reported with default runtime configuration. I can't imagine a situation where it would be desirable for a program to silently crash. It definitely shouldn't be a default behaviour.
Ah, I agree, my bad
Thank you.
Nightmare is a great tool. Important part of our monitoring is running on it and I really appreciate the hard work your are putting into it's development. Keep it up :-)
We'll be tracking this one in #1233. Thanks for bringing it up!
Steps to reproduce:
Have some kind of virtualisation (VM, Docker for Mac, etc.) with shared project folder.
Install nightmare in your host OS (say OS X):
Prepare following test script:
and save it
arch.js
.Run it:
Now run it in your virtual machine with different platform (say Linux):
Expected result:
I'd like to get some kind of error that I could handle.
I know what's wrong, but it's not very friendly, especially for colleagues who are not very experienced with Node.js. In local development it can happen quite often that you run dependency installation on your host instead of VM or the other way around. It can be confusing and time wasting.