When ran non-literally this code is fine. However, if this file has been encoded. the ‘u2028’ literally reads ‘PARAGRAPH_BREAK’ which is not a valid value for a variable in an object literal; it will tell you there is an unexpected , in this case.
For me, this showed up in my build process. I tend to concatenate my JS and serve it as a single file; decreasing http calls and speeding up a websites loading. For this I use Google’s Closure Compiler. I also like to compile my language files into the mix, and these by definition need to be in Unicode. However, something curious occurs when running the next command.
A bug report has been filed with closure compiler, but I’m not sure that’s something closure will want to deal with. Bug Report
Update: This bug has been fixed.