The newer version of socket.io can act as an AMD (RequireJS) module. It auto-detects and will not expose its globals when RequireJS is being used.

It's better that way, but the kernel needs to convert to a RequireJS module before it can load socket.io as a dependency.

Until then (sandbox branch), we need it to act the old way, which it will if it loads before RequireJS.


On Sep 20, 2013, at 10:25 AM, eric79 <notifications@github.com> wrote:

> In support/client/lib/index.html:
> 
> > @@ -42,8 +45,6 @@
> >      <script type="text/javascript">goog.require('goog.vec.Quaternion')</script>
> >  
> >      <script type="text/javascript">if (!window.WebSocket && window.MozWebSocket) window.WebSocket=window.MozWebSocket</script> <!-- for Firefox 5 -->
> > -    <script type="text/javascript" src="socket.io.js"></script>
> > -    <script type="text/javascript" src="socket.io-sessionid-patch.js"></script>
> I don't have any real concerns ... but I'm curious why socket.io.js was moved to the top of the list of loaded scripts.
> 
> —
> Reply to this email directly or view it on GitHub.