Package Exports
- socket.io-client
- socket.io-client/dist/socket.io
- socket.io-client/dist/socket.io.dev.js
- socket.io-client/dist/socket.io.dev.js.map
- socket.io-client/dist/socket.io.js
- socket.io-client/dist/socket.io.js.map
- socket.io-client/dist/socket.io.slim
- socket.io-client/dist/socket.io.slim.js
- socket.io-client/lib/socket
- socket.io-client/package
- socket.io-client/package.json
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (socket.io-client) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
socket.io-client
How to use
A standalone build of socket.io-client is exposed automatically by the
socket.io server as /socket.io/socket.io.js. Alternatively you can
serve the file socket.io.js found in the dist folder.
<script src="/socket.io/socket.io.js"></script>
<script>
var socket = io('http://localhost');
socket.on('connect', function(){});
socket.on('event', function(data){});
socket.on('disconnect', function(){});
</script>// with ES6 import
import io from 'socket.io-client';
const socket = io('http://localhost');A slim build (without JSON3, a JSON polyfill for IE6/IE7, and debug) is also available: socket.io.slim.js.
Socket.IO is compatible with browserify and webpack (see example there).
Node.JS (server-side usage)
Add socket.io-client to your package.json and then:
var socket = require('socket.io-client')('http://localhost');
socket.on('connect', function(){});
socket.on('event', function(data){});
socket.on('disconnect', function(){});API
See API