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

@davestewart/nuxt-sockets

v0.1.0

Published

WebSockets solution for Nuxt

Downloads

3

Readme

Nuxt Sockets

Nuxt wrapper for Vue 3 Perfect Scrollbar

npm version npm downloads License Nuxt

Overview

Nuxt Sockets implements bidirectional sockets communication between Nitro and Nuxt.

It supports named channels making it ideal for plugin authors.

// server
const socket = useSocketServer('my-plugin')
socket.send('ping!')
// client
const socket = useSocketClient('my-plugin', ({ channel: string, data: any }) => {
  console.log(data) // ping!
})

Demo

To view the demo live on StackBlitz:

  • https://stackblitz.com/github/davestewart/nuxt-sockets?file=playground%2Fapp.vue

To run the demo locally:

npm run dev

Quick Setup

Installation:

npm install --save @davestewart/nuxt-sockets

Configuration:

export default defineNuxtConfig({
  modules: [
    '@davestewart/nuxt-sockets'
  ],
})

Usage

Server

Here's how you might set up the server to watch some files, then report them to the frontend:

// module.ts
import { createStorage } from 'unstorage'
import { useSocketServer } from '@davestewart/nuxt-sockets'

export default function (options, nuxt) {
  // create the server
  const socket = useSocketServer('my-plugin')
  
  // watch files for changes
  const storage = createStorage(dirname)
  storage.watch(function (event, key) => {            
    socket.send({ event, key })              
  })
  
  // handle incoming messages
  socket.onMessage(({ data }) => {
    console.log('message:', data)
  })
}

Client

The client should take the same name as the server, so calls are sent between the two, and they don't clash with any other services using sockets.

export default defineNuxtPlugin(async () => {
  if (process.client) {
    // receive a message
    const socket = await useSocketClient('my-plugin', ({ data }) => {
      console.log('file changed', data)
    })
    
    // send a message
    window.addEventListener('click', () => {
      socket.send('user clicked')
    })
  }
})

Alternative setups

You can create a Socket instance in several ways:

// generic server (not recommended)
const socket = useSocketServer()

// named server
const socket = useSocketServer('some-name')

// named server and default handler
const socket = useSocketServer('some-name', ({ channel, data }) => {
  console.log({ channel, data })
})

// named server and filter handler
const socket = useSocketServer('some-name').addHandler<Bar>('foo', ({ data }) => {
  console.log(data.baz)
})

The library also has some generic typing, so you can hint the return data type:

// example types
type Foo = { foo: string }
type Bar = { bar: string }
type Baz = { baz: string }

// hint the composable
const socket = useSocketServer<Foo>('plugin', ({ data }) => {
  console.log(data.foo)
})

// hint the handler
const socket = useSocketServer<SomeClass>('plugin', ({ data }) => {
  console.log(data.bar)
})


// hint the handler
const socket = useSocketServer<SomeClass>('plugin').addHandler<Bar>('foo', ({ data }) => {
  console.log(data.baz)
})

Filtering

The module supports basic filtering, but this may be taken out in the next version.

Development

To develop the module:

# develop the module using the demo
npm run dev

# build and release (make sure to update version and changelog first)
npm run release