
Security News
The Hidden Blast Radius of the Axios Compromise
The Axios compromise shows how time-dependent dependency resolution makes exposure harder to detect and contain.
It is fork from https://github.com/bougarfaoui/ng-io
I have add Angular 5 SSR support and made the library with https://github.com/gonzofish/angular-librarian
Also, I have add option connectOnAppLoad which allow socket to connect on app load (true by default).
Here is working example with universal
npm install ng-io
//...
import { NgIoModule, NgIoConfig } from 'ng-io';
const config: NgIoConfig = { url: 'http://localhost:8988', options: {} };
@NgModule({
declarations: [
AppComponent
],
imports: [
BrowserModule,
NgIoModule.forRoot(config)
],
providers: [],
bootstrap: [AppComponent]
})
export class AppModule { }
We need to configure NgIoModule module using the object config of type NgIoConfig, this object accepts two optional properties they are the same used here io(url[, options]).
Now we pass the configuration to the static method forRoot of NgIoModule
The NgIoModule provides now a configured SocketIo service that can be injected anywhere inside the AppModule.
import { Injectable } from '@angular/core';
import { SocketIo } from 'ng-io';
@Injectable()
export class ChatService {
constructor(private socket: SocketIo) { }
sendMessage(msg: string){
this.socket.emit("message", msg);
}
getMessage() {
return this.socket
.fromEvent("message")
.map( data => data.msg );
}
}
In this case we do not configure the NgIoModule directly using forRoot. What we have to do is: extend the SocketIo service, and call super() with the NgIoConfig object type (passing url & options if any).
import { Injectable, NgModule } from '@angular/core';
import { SocketIo } from 'ng-io';
@Injectable()
export class SocketOne extends SocketIo {
constructor() {
super({ url: 'http://url_one:portOne', options: {} });
}
}
@Injectable()
export class SocketTwo extends SocketIo {
constructor() {
super({ url: 'http://url_two:portTwo', options: {} });
}
}
@NgModule({
declarations: [
//components
],
imports: [
NgIoModule,
//...
],
providers: [SocketOne, SocketTwo],
bootstrap: [/** AppComponent **/]
})
export class AppModule { }
Now you can inject SocketOne, SocketTwo in any other services and / or components.
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.on(eventName: string)Takes an event name and callback. Works the same as in SocketIo.IO.
socket.removeListener(eventName: string, callback: Function)Takes an event name and callback. Works the same as in SocketIo.IO.
socket.removeAllListeners(eventName: string)Takes an event name. Works the same as in SocketIo.IO.
socket.emit(eventName:string, message: any, [callback: Function])Sends a message to the server. Optionally takes a callback. Works the same as in SocketIo.IO.
socket.fromEvent<T>(eventName: string): Observable<T>Takes an event name and returns an Observable that you can subscribe to.
Takes an event name, and returns a Promise instead of an Observable.
Works the same as once in SocketIo.IO.
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.
You can also see this example with express.js.
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { AppComponent } from './app.component';
import { NgIoModule, NgIoConfig, SocketIo} from 'ng-io';
const config: NgIoConfig = { url: 'http://localhost:8988', options: {} };
@Injectable()
class ChatService {
constructor(private socket: SocketIo) { }
sendMessage(msg: string){
this.socket.emit("message", msg);
}
getMessage() {
return this.socket
.fromEvent<any>("message")
.map(data => data.msg );
}
close() {
this.socket.disconnect()
}
}
@NgModule({
declarations: [
AppComponent
],
imports: [
BrowserModule,
NgIoModule.forRoot(config)
],
providers: [ChatService],
bootstrap: [AppComponent]
})
export class AppModule { }
``
## LICENSE
MIT
FAQs
Angular 4+ module for socket.io
The npm package ng-io receives a total of 1 weekly downloads. As such, ng-io popularity was classified as not popular.
We found that ng-io demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
The Axios compromise shows how time-dependent dependency resolution makes exposure harder to detect and contain.

Research
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.

Research
Malicious versions of the Telnyx Python SDK on PyPI delivered credential-stealing malware via a multi-stage supply chain attack.