ngx-socket-io
Version:
Socket.IO module for Angular
198 lines (140 loc) • 6.14 kB
Markdown
# ngx-socket-io
[](https://travis-ci.org/rodgc/ngx-socket-io)
[](https://badge.fury.io/js/ngx-socket-io)
[](https://github.com/rodgc/ngx-socket-io)
[Socket.IO](http://socket.io/) module for Angular
## Install
`npm install ngx-socket-io`
**Important:**
Make sure you're using the proper corresponding version of socket.io on the server.
| Package Version | Socket-io Server Version | Angular version |
| --------------- | ------------------------ | --------------- |
| v3.4.0 | v2.2.0 | |
| v4.1.0 | v4.0.0 | 12.x |
| v4.2.0 | v4.0.0 | 13.x |
| v4.3.0 | v4.5.1 | 14.x |
| v4.4.0 | v4.5.1 | 15.x |
| v4.5.0 | v4.5.1 | 16.x |
| v4.6.1 | v4.7.2 | 17.x |
| v4.7.0 | v4.7.2 | 18.x |
| v4.8.1 | v4.8.1 | 19.x |
## How to use
### Import and configure SocketIoModule for NgModule based applications
```ts
import { SocketIoModule, SocketIoConfig } from 'ngx-socket-io';
const config: SocketIoConfig = { url: 'http://localhost:8988', options: {} };
({
declarations: [AppComponent],
imports: [BrowserModule, SocketIoModule.forRoot(config)],
providers: [],
bootstrap: [AppComponent],
})
export class AppModule {}
```
We need to configure `SocketIoModule` module using the object `config` of type `SocketIoConfig`, this object accepts two optional properties they are the same used here [io(url[, options])](https://socket.io/docs/v4/client-initialization/#Options).
Now we pass the configuration to the static method `forRoot` of `SocketIoModule`
### Import and configure SocketIoModule for standalone based applications
In app.config.ts use the following:
```ts
import { ApplicationConfig, importProvidersFrom } from '/core';
import { SocketIoModule, SocketIoConfig } from 'ngx-socket-io';
const config: SocketIoConfig = { url: 'http://localhost:8988', options: {} };
export const appConfig: ApplicationConfig = {
providers: [provideSocketIo(config)],
};
```
In standalone applications, there is no `AppModule` to import `SocketIoModule`. Instead, we use `provideSocketIo(config)` directly in the providers' configuration. The usage of the socket instance remains the same as in an NgModule-based application.
### Using your socket Instance
The `SocketIoModule` provides now a configured `Socket` service that can be injected anywhere inside the `AppModule`.
```typescript
import { Injectable } from '/core';
import { Socket } from 'ngx-socket-io';
import { map } from 'rxjs/operators';
()
export class ChatService {
constructor(private socket: Socket) {}
sendMessage(msg: string) {
this.socket.emit('message', msg);
}
getMessage() {
return this.socket.fromEvent('message').pipe(map(data => data.msg));
}
}
```
### Using multiple sockets with different end points
In this case we do not configure the `SocketIoModule` directly using `forRoot`. What we have to do is: extend the `Socket` service, and call `super()` with the `SocketIoConfig` object type (passing `url` & `options` if any).
```typescript
import { Injectable, NgModule } from '/core';
import { Socket } from 'ngx-socket-io';
()
export class SocketOne extends Socket {
constructor() {
super({ url: 'http://url_one:portOne', options: {} });
}
}
()
export class SocketTwo extends Socket {
constructor() {
super({ url: 'http://url_two:portTwo', options: {} });
}
}
({
declarations: [
//components
],
imports: [
SocketIoModule,
//...
],
providers: [SocketOne, SocketTwo],
bootstrap: [
/** AppComponent **/
],
})
export class AppModule {}
```
Now you can inject `SocketOne`, `SocketTwo` in any other services and / or components.
## API
Most of the functionalities here you are already familiar with.
The only addition is the `fromEvent` method, which returns an `Observable` that you can subscribe to.
### `socket.of(namespace: string)`
Takes a namespace and returns an instance based on the current config and the given namespace,
that is added to the end of the current url.
See [Namespaces - Client Initialization](https://socket.io/docs/v4/namespaces/#client-initialization).
Instances are reused based on the namespace.
### `socket.on(eventName: string, callback: Function)`
Takes an event name and callback.
Works the same as in Socket.IO.
### `socket.removeListener(eventName: string, callback?: Function)`
Takes an event name and callback.
Works the same as in Socket.IO.
### `socket.removeAllListeners(eventName?: string)`
Takes an event name.
Works the same as in Socket.IO.
### `socket.emit(eventName:string, ...args: any[])`
Sends a message to the server.
Works the same as in Socket.IO.
### `socket.fromEvent<T>(eventName: string): Observable<T>`
Takes an event name and returns an Observable that you can subscribe to.
### `socket.fromOneTimeEvent<T>(eventName: string): Promise<T>`
Creates a Promise for a one-time event.
You should keep a reference to the Observable subscription and unsubscribe when you're done with it.
This prevents memory leaks as the event listener attached will be removed (using `socket.removeListener`) ONLY and when/if you unsubscribe.
If you have multiple subscriptions to an Observable only the last unsubscription will remove the listener.
## Know Issue
For `error TS2345` you need to add this to your `tsconfig.json`.
```json
{
...
"compilerOptions": {
...
"paths": {
"rxjs": ["node_modules/rxjs"]
}
},
}
```
## Related projects
- [bougarfaoui/ng-socket-io](https://github.com/bougarfaoui/ng-socket-io) - Socket.IO module for Angular
## LICENSE
MIT