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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@mygo-plugins/websocket

v0.2.6

Published

A WebSocket whose connections Go makes, for MyGo desktop apps

Readme

@mygo-plugins/websocket

A WebSocket for MyGo apps whose connections Go makes, with the API of the browser's. Unlike the browser's, it may send any header with the opening handshake, such as Authorization, Cookie or Origin, and is not subject to the page's Content Security Policy.

Use the plugin in Go:

import "github.com/egoist/mygo/plugins/websocket"

mygo.Use(websocket.Plugin) // or websocket.New(websocket.Options{...})

and connect in the frontend:

import { WebSocket } from "@mygo-plugins/websocket";

const ws = new WebSocket("wss://example.com/live", ["v1"], {
  headers: { authorization: `Bearer ${token}` },
});
ws.onopen = () => ws.send("hello");
ws.onmessage = (e) => console.log(e.data);
ws.onclose = (e) => console.log(e.code, e.reason, e.wasClean);

Messages are sent in order, bufferedAmount counts the bytes Go has not written yet, and received messages wait in Go while the page is behind, so a fast server cannot fill the page's memory. Connections close (1001, going away) when their page navigates away or its window closes. No extensions (such as permessage-deflate) are negotiated.

The documentation covers closing, failures and the options of the Go side.