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

@cepharum/ipp

v0.1.2

Published

parsing and creating IPP messages

Downloads

10

Readme

IPP Message Processor

pipeline status coverage report

(c) cepharum GmbH, http://cepharum.de

License

MIT

About

This library provides parsing and generation of RFC8011 IPP messages. In addition it contains code for parsing IPP message from stream forwarding all body data following parsed IPP message to be processed separately, e.g. for storing or instantly processing it. Eventually, there is a middleware for use with express or compatible server applications to conveniently discover IPP messages in incoming requests.

Install

npm i @cepharum/ipp

Usage

const { IPPMessage } = require( "@cepharum/ipp" );

const parsed = new IPPMessage( rawMessage );
const response = parsed.deriveResponse();
const encoded = response.toBuffer();

It comes with a middleware generator suitable for use with Express server-side framework:

const IPP = require( "@cepharum/ipp" );

app.use( IPP.middleware() );

app.post( ( req, res ) => {
    // req.body.message is instance of IPPMessage here
    // req.body.data is a Readable stream providing payload of IPP message
} );

The same middleware generator is suitable for injecting into Hitchy server-side framework as well:

const IPP = require( "@cepharum/ipp" );

exports.policies = {
    "POST /": IPP.middleware(),
};

exports.routes = {
    "POST /"( req, res ) {
        // this.local.ipp.message is instance of IPPMessage here
        // this.local.ipp.data is a Readable stream providing payload of IPP message
    }
};

Relax Syntax Rules

When implementing IPP services there are some situations when RFC 8011 is contradictory in itself, when it comes to enforcing syntax rules on keywords in section. By supporting global options you can put this library into relaxed mode:

const IPP = require( "@cepharum/ipp" );

IPP.setGlobalOption( "relaxKeywordSyntax", true );

...