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

linejs

v0.1.1

Published

A configurable, scalable & elegant Node.js standalone WAMP router based on the WAMP websocket subprotocl

Readme

Line Logo

$ npm install -g linejs && line

About

npm version

Line is all about...

Getting Started

At the moment (v0.1.0) Line is a thin command-line wrapper around the nightlife-rabbit WAMP router developed by . It enforces the standalone requirement of the WAMP specification by encapsulating the logic into a lightweight command line tool to run a standalone NodeJS WAMP router. As such, to run the router, simply run the line command:

$ line

And it will fire up a simple WAMP router. There are presently three configurable options as follows (you can access this by running line -h):

Options:

    -h, --help          output usage information
    -v, --version       output the version number
    -p, --port [value]  The port the router will listen on (defaults to 3131)
    -P, --path [value]  The path of the websocket connection (defaults to /line)
    -o, --autoOff       Disable auto realm creation if the realm does not exist (defaults to false)

FAQ

Is LineJS a Node.js WAMP router?

No, LineJS does not try to be a WAMP router and neither should it be used as such. LineJS is a framework or template to be used and configured to build next generation realtime web APIs to replace RESTful HTTP APIs.

Why isn't LineJS a WAMP router?

Because that's not what it is. There already exist several open source WAMP routers including the officially supported Crossbar.io project which can run NodeJS application logic.

If LineJS isn't a WAMP router how can it use WAMP?

This question is usually asked because of a fundemental misunderstanding of WAMP. WAMP is a protocol, just like HTTP. And it can be used in many different ways. For example, REST (REpresentational State Transport) is a way to use HTTP. But one could just as easily use the HTTP protocol in ways that would violate RESTful principles. In much the same way, WAMP functions as a subprotocl based on websockets. Unfortunately, the WAMP spec includes one opiniated requirement that systems using WAMP should always use routers. We believe this is a fundemtal flaw in the WAMP spec since a communication spec should not worry about architecture. As a result, we've taken an approach very similar to existing HTTP APIs which combines the power and flexiblity of WAMP with the proven architecture of HTTP APIs and combined them to get LineJS. We like to think of it as a cross between generic HTTP APIs and WAMP. Or you could call it a hybrid WAMP solution.

So does that mean LineJS violates the WAMP protocl spec?

Yes, LineJS does violate the one requirement that those implementing the WAMP spec use routers. As a result, LineJS is NOT WAMP compliant. In all other aspects, however, LineJS does correctly implement the WAMP spec.