There's nothing wrong with your JSON file but, according to the console log, it seems your web server does not set correct response header Content-Type
which should be application/json
.
So your browser tries to interpret your file as a JavaScript file and find an invalid token.
For instance with Nginx, you could use mime type configuration file provided by HTML5-Boilerplate project (https://github.com/h5bp/server-configs-nginx/blob/master/mime.types) and include it into your Nginx configuration:
include /etc/nginx/mime.types;
It contains the following directive setting application/json
as content type for JSON:
types {
application/json json;
}