One other gotcha that can result in "SyntaxError: Unexpected token" exception when calling JSON.parse() is using any of the following in the string values: New-line characters.
Same problem here; bat script: ... produces "f was unexpected at this time." I'm an old Unix csh script/regex guy, so this new syntax is tripping me up.
That means when we reach 3, the start of a new string using double quotes, it's an unexpected string. You probably want: ... At 1, we start the string. 2 is just a " within the string, it doesn't end it. 3 ends it, then we append checkval, then we start a new string (4) with a " in it (5) followed by a ] and then the end of the string (6).
Unexpected indent. This line of code has more spaces at the start than the one before, but the one before is not the start of a subblock (e.g., the if, while, and for statements).
This is why you're getting the "Unexpected token '<'" error, because the HTML is not valid JSON. To fix this issue, you need to check what the server is sending back and make sure it's returning a JSON object.
How to fix SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not ...
Python unexpected EOF while parsing [duplicate] Asked 15 years, 1 month ago Modified 1 year, 5 months ago Viewed 501k times
SyntaxError: Unexpected identifier Asked 11 years, 2 months ago Modified 1 year, 8 months ago Viewed 118k times
Error: Uncaught SyntaxError: Unexpected token < Asked 15 years, 7 months ago Modified 1 year, 4 months ago Viewed 312k times