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

lpt

v0.4.0

Published

High level binding to deal with parallel ports (linux only)

Readme

node-lpt

High-level bindings to parallel port for node.js.

Important: this module works only under linux through the parport driver, so you might need to compile kernel or modules (on gentoo mostly).

Installation

$ npm install lpt

Usage

var lpt = require('lpt')
  , port = new lpt.Port(0, 'byte', false) // open /dev/parport0 with forced `byte` mode set
  // , port = new lpt.Port(0) // the same

console.log(port.data) // read data register
console.log(port.status.busy) // get /BUSY pin status

port.data = 123 // write data register
port.control.init = true // write to control register

API

Constructor receives the following parameters:

  • port number
  • parallel port mode - optional. Can be:
    • spp
    • nibble
    • byte - default
    • epp
    • ecp
  • negotiate port - optional. If true will try IEEE 1284 compliant mode negotiation.

Port class provides next fields:

| Field | Type | Description | Read/Write | Pin num | | --------------- | ---- | ------------- |:----------:| -------:| | data | byte | Data register | R/W | 2..9 | | control.init | bool | INIT | R/W | 16 | | control.select | bool | /SELECT_IN * | R/W | 17 | | control.autofd | bool | /AUTO_FEED * | R/W | 14 | | control.strobe | bool | /STROBE * | R/W | 1 | | status.ack | bool | ACK | R | 10 | | status.busy | bool | /BUSY * | R | 11 | | status.error | bool | ERROR | R | 15 | | status.select | bool | SELECT | R | 13 | | status.paperOut | bool | PAPEROUT | R | 12 | | - | - | Ground | - | 18..25 |

*Note that this pins are inverted by node-lpt itself

**You can read control pins only after you wrote something to it. Before that moment you can't rely on pin status

Useful links

License

MIT