Closed d3v-null closed 5 years ago
Also I've noticed that even putting comments under valid JS will completely break slate.
if my .slate.js file is
slate.log("HELLO");
it will output hello in the log, but if my .slate.js file is
slate.log("HELLO");
//Comment
It won't output anything. This however works fine:
//Comment
slate.log("HELLO");
This is pretty frustrating :/
Hey there, I have OSX El Cap and Slate v1.2 running with only a .slate.js file in my home directory and I was trying to debug my code by looking at the console, but couldn't figure out what was wrong with it because slate wouldn't even run my calls to log. I discovered that certain invalid javascript is not picked up by slate, and instead of telling the user that there is something wrong with their code, slate will just exit.
Here's what my file looked like
Here is the console log when the bad JS is commented out
And here it is with the JS uncommented
Also I think the console log is a bit concerning, is it normal to have that many errors?