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

telnet-socket

v0.2.4

Published

A standards compliant Telnet implementation for Node.js

Readme

telnet-socket

A standards compliant Telnet implementation for Node.js

Standards

In addition to RFC 854, a number of additional RFCs, proposed RFCs, and adopted options such as GMCP and MSSP are implemented. An emphasis on standards used with ANSI-BBS related terminals is taken, though PRs are certainly welcome if something of use is missing.

Some additional standards include:

See telnet_spec.js for more information and additional standards.

Usage

const { TelnetSocket, TelnetSpec } = require('telnet-socket');

const telnetSocket = TelnetSocket(rawSocket);

//	request client to send NAWS
telnetSocket.do.naws();

telnetSocket.on('SB', command => {
	if (TelnetSpec.Options.NAWS === command.option) {
		// client sent us NAWS
		const { width, height } = command.optionData;
		// ...do something with height and width
	}
});

The TelnetSocket Class

Properties

  • passthrough: Set to true to enable passthrough mode. Defaults to false.
  • escapeIACs: Set to false to disable escaping of telnet IAC characters. Defaults to true.
  • rawSocket: Access the underlying socket.

Events

General

  • data (data): Non-protocol data
  • command error (command, error): An error ocurred whilest processing a command.
  • end (): Socket end.
  • error (error): A socket error has occurred.

Commands

Events are emitted for specific Telnet commands such as (but not limited to) DO, DONT, WILL, WONT and AYT with the signature of (command) where command has the following properties:

  • code: The raw byte code of the command.
  • name: The command name (DO, DONT, ...) or unknown comand.
  • option: Option sent with the command.
  • optionName: The name of the option such as NAWS or unknown option.
  • optionData: For options that contain additional data. For example, NAWS contains height and width members, while TTYPE contains a ttype member.

Unknown commands are emitted as unknown command with the same signature described above.

License

See LICENSE.md