Hi,
I have found the problem. It appears that one of the scripts running on the page defines the variable called “exports” which is used for loading nodeJS modules. The search script loader was trying to load itself as a module, but failed.
I’ve fixed the problem by turning off the “Load scripts in footer” option on the Compatibility Options submenu: http://i.imgur.com/Xfl0DJP.png
I will investigate this issue further on my local environment, so the next update will contain some kind of bypass for similar situations. Just to make sure in the future nobody else gets the same error.