npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@decorators/socket

v3.4.1

Published

node decorators - decorators for socket.io library

Downloads

69

Readme

Node Decorators

Project implements decorators for Socket.IO

Installation

npm install @decorators/socket --save

API

Decorators

Class
  • @Controller(namespace?: string, middleware?: Middleware[]) - registers controller for controller
Method
  • @Connection(middleware?: Middleware[]) - register connection listener (io.on('connection', fn))
  • @Connect(middleware?: Middleware[]) - alias of @Connection()
  • @Disconnect(middleware?: Middleware[]) - register disconnect socket event (socket.on('disconnect', fn))
  • @GlobalEvent(event: string) - register global event (io.on)
  • @Event(event: string, middleware?: Middleware[]) - register socket event (socket.on)
Parameter
  • @IO(WrapperClass?: Class) - returns server itself
  • @Socket(WrapperClass?: Class) - returns socket If WrapperClass provided, returns instance of WrapperClass, passes socket or server as dependency into WrapperClass
class SocketWrapper {
  constructor(
    private ioSock: SocketIO.Server|SocketIO.Namespace|SocketIO.Socket
  ) {}
}
  • @Args() - returns event arguments (excluding callback, if it exists)
  • @Ack() - returns ack callback function (if it exists)

Helper Functions

  • attachControllers(io: SocketIO.Server, Controller[]) - Attaches controllers to IO server
Middleware

Middleware is a class, that implements interface Middleware, like so:

class ControllerMiddleware implements Middleware {
  public use(
    io: SocketIO.Server | SocketIO.Namespace,
    socket: SocketIO.Socket,
    args: any,
    next: Function
  ) {
    console.log('ControllerMiddleware');
    next();
  }
}

To register global middleware handler create a class, that implements interface ServerMiddleware, like so:

class GlobalMiddleware implements ServerMiddleware {
  public use(
    io: SocketIO.Server | SocketIO.Namespace,
    socket: SocketIO.Socket,
    next: Function
  ) {
    console.log('GlobalMiddleware');
    next();
  }
}

Then register it by using IO_MIDDLEWARE injection token with Container from @decorators/di package, like so:

Container.provide([
  { provide: IO_MIDDLEWARE, useClass: GlobalMiddleware }
]);

Details

Middleware

The middleware order :

  • Global Server Middleware (io.use(...))
  • Controller based middleware (@Controller(...))
  • Event based middleware (@Event(...))

Additionally to this order depends on the order how you've registered appropriate types of middleware

Quick Example:

import { listen } from 'socket.io';
import { Event, Args, attachControllers, Controller } from '@decorators/socket';

const server = listen(3000);

@Controller('/')
class MessageController {

  @Event('message')
  onMessage(@Args() message) {
    console.log(
      `Message:  ${message}`
    );
  }

}

attachControllers(server, [ MessageController ]);