Uncaught SyntaxError: Unexpected end of input error in Chrome

Today, while I was working with jQuery I ran on this error Uncaught SyntaxError: Unexpected end of input while troubleshooting my code in Chrome. And since Chrome it didn’t report error on any specific line I had to Google for it 🙂

Uncaught SyntaxError: Unexpected end of input

And after opening few pages I found out that this error codes happens when you forget closing “}”. That can happen often when writing JavaScript code.

Locating that is not easy, especially if you’r code is sloppy and you have a lot of it. Luckily my code is always very nicely written so I got it solved quickly. But in case your code is really messy or is compressed (with some JavaScript compressing tool like jscompress.com) you can copy/paste your JavaScript code into jsbeautifier.org, click on Beautify JavaScript (select the options you want on the right side of the screen first) and see if all of the indentations are correct.

Beautiful and Geeky.

Tags: Uncaught SyntaxError: Unexpected end of input, uncaught syntaxerror unexpected end of input line 1, unexpected end of input, uncaught, uncaught syntaxerror unexpected end of input, unexpected end of input line 1, javascript unexpected end of input line 1, javascript unexpected end of input, jquery unexpected end of input, syntaxerror: unexpected end of input, uncaught syntaxerror: unexpected end of input line 1, syntaxerror unexpected end of input, UncaughtSyntaxError:UnexpectedendofinputerrorinChrome|GeekTipsnTricks, decompression problem unexpected end of input file or i/o error, unexpected end of input js, uncaught syntaxerror unexpected end of input jquery, onclick unexpected end of input, decompression problem unexpected end of input file or i o error, unexpected end of input javascript line 1

View Comments

  • I just got this error and all my braces were perfect. In fact, all my code was ... erm.. "perfect".
    For me the problem turned out to be improperly formed JSON data I was getting from the server. For some reason the data was truncated (thus naturally missing a few closing braces) and it blew up in JSON.parse() - which kind of makes it seem like JSON.parse is using eval() which I thought it shouldn't, but Chrome seemed to be giving me this error at the top of the function in which the JSON.parse() was being called. It was very perplexing until I took a look at what data was coming across the wire.

Share
Published by
Nick

Recent Posts

How to Manage Storage on Smartphone: 12 Ways

Can't download new apps to your phone because there isn't enough storage space? Lack of…

10 months ago

Spotlight Search won’t open the files it finds in Dropbox with associated application

This issue started to appear on macOS 13 Ventura after recent Dropbox update. I would…

1 year ago

Windows 10 Search fix

Since this morning (Feb 5th 2020) search just stopped working on my Windows 10 (version…

4 years ago

The mysql_result in mysqli

Many of you have run into a problem when you were working on some old…

4 years ago

How to convert physical Windows PC into a virtual machine

After 10 years of running my main desktop computer on Windows 7 - time has…

4 years ago

How to downgrade PHP 7.4 to PHP 7.3 on VestaCP running on CentOS 7

I installed VestaCP for a clien on a new dedicated server running CentOS 7. Once…

4 years ago