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

@4qwerty7/syspipe

v0.1.5

Published

Access to the operating system native pipe implementation

Downloads

6

Readme

Syspipe

Build Status

node.js module to access operating system native pipe implementation. For more info check "man 2 pipe"

This interface simply gives you the ability to call the operating system pipe system call. It will return an object with the input and output file descriptors

$ node
> require('syspipe').pipe()
{ read: 13, write: 14 }

This is generally not useful for most node program, as the pipe has a limited size imposed by the os, and if you exceed that your program will block until it is read -- and since node is single threaded by nature, you will not be able to read from the pipe and you end up deadlocked.

However where this extension is useful, is if you have a native threaded extension which requires data to be read from a FD, then is a handy way of passing data from the node envirionment to the extension.

Install

$ npm install syspipe

Usage

var fs = require('fs');
var syspipe = require('syspipe');

var buf = new Buffer(1024);
var read = 0;

var pipe = syspipe.pipe();
fs.writeSync(pipe.write, 'hello world');
read = fs.readSync(pipe.read, buf, 0, 1024, null);

console.log('Pipe read: ' + buf.slice(0, read).toString());

Native pipes can also be useful to interact with child processes executed from node.js in a sync manner.

Example:

var proc = require('child_process');
var fs = require('fs');
var syspipe = require('syspipe');

var buf = new Buffer(1024);
var read = 0;


var pipe = syspipe.pipe();
var options = { stdio: ['pipe', pipe.write, 'pipe'] };
var ls = proc.spawn('r2', ['-q0', '/bin/ls'], options);

var OUT = pipe.read;
var IN = ls.stdin['_handle'].fd;


read = fs.readSync(OUT, buf, 0, 1024, null);
console.log('[+] read ' + read + ' bytes');

fs.writeSync(IN, 'f\n');
read = fs.readSync(OUT, buf, 0, 1024, null);
var result = buf.slice(0, read-1);

console.log(result.toString());
console.log('[+] Read: ' + read + ' bytes');

fs.writeSync(IN, 'q\n');