No feedback on SyntaxError #95
Comments
No, that's the problem, I don't even get a message in the console, which would be fine. |
Ok, something weird just happened. I tried to reproduce the issue on my home laptop (archlinux, node 10), and got the same result using the 1.0.18 version from npm. Not sure what happened, but I'll check if I can reproduce with my work setup (on monday). |
Thanks for your report, I will close it for now. Feel free to reopen it if it still reproducible on your machine at work. |
Thanks, could you tell what terminal do you use? Based on screenshot it does not look like regular bash :) |
Thanks! Couple more questions: could you open DevTools on ndb by pressing Ctrl + Shift + I and copy paste console output here if there anything and update to latest ndb version 1.0.20 and verify that it is still reproducible? |
Thanks! I finally can reproduce it locally and am working on fix. |
It looks to me that the root of the issue is combination of "Pause on exception" toggle, "Blackbox anything outside working directory" checkbox from Settings and Node 8. You can disable "Pause on exception" to get SyntaxError in console. |
) - latest DevTools frontend contains automapping fix, - backend fs fix fetching content of small files. Helps with #95
Unfortunately it is too late to fix Node 8, please use Node 10 if it is possible. |
Steps to reproduce
Tell us about your environment:
What steps will reproduce the problem?
ndb test.js
What is the expected result?
Some feedback that there is a syntax error
What happens instead?
No feedback, nothing happens
The text was updated successfully, but these errors were encountered: