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

vite-sveltekit-node-ws-global

v0.0.1

Published

NOTE: THis is a modified version of vite-sveltekit-node-ws with some custom changes. Once (or if) those changes are merged into the master repository this one will be removed.

Downloads

3

Readme

vite-sveltekit-node-ws-global

NOTE: THis is a modified version of vite-sveltekit-node-ws with some custom changes. Once (or if) those changes are merged into the master repository this one will be removed.

This plugin just exposes httpServer without any dependencies. In theory, you can use any websocket framework you like.

Try it with socket.io

Support

  • dev
  • preview
  • online

Usage

vite.config.ts

import { sveltekit } from '@sveltejs/kit/vite';
import { defineConfig } from 'vitest/config';
import ws from 'vite-sveltekit-node-ws';

export default defineConfig({
    plugins: [sveltekit(), ws({global: true})]
});

hooks.server.ts

import {useServer} from "vite-sveltekit-node-ws";
import {WebSocketServer} from 'ws'

useServer({
    global: true, //This is optional, uses global namespace rather than local namespace
    callback: (server) => {
        const ss = new WebSocketServer({server})
        ss.on('connection',a=>{
            a.on('message',e=>{
                a.send(`echo: ${e}`)
            })
        })
    },
    skip: (pathname:string)=>{
        // It is optional 
        // You can block some requests to prevent them from being processed by SveltetKit
        // return pathname.startsWith('/hello')
        return false
    }})

API

import wsPlugin, {useServer} from "vite-sveltekit-node-ws";

wsPlugin({hmrPort?: number | false; buildModification?: string; global?: boolean; })

  • hmrPort: Specify the port of hmr in vite config. If set to false, then no port modifications will be done
  • global: Sets the httpServer that the ws server is connected to to be in the global namespace rather than local.
  • buildModifiation: Sets the modification to the index file. Not requierd to be set.

useServer({callback: serverHandle, skip: pathHandle?, global?: boolean})

serverHandle: ( server ) => void
pathHandle?:  ( pathname: string ) => boolean 
  • server : the httpServer from Polka(production mode) or from Vite(development.preview mode)
  • pathHandle: return true if the request no need to be handled by sveltekit
  • pathname: the request's pathname
  • global: sets the request to use the global namespace. Should be set to the same as wsPlugin.