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

parsedmessage

v3.1.0

Published

ParsedMessage is an ultra-lightweight extension of IncomingMessage: url.parse and querystring.parse called via getter methods on .path, .query, and others

Downloads

19

Readme

ParsedMessage

Since Node v9.6.0, http.createServer supports an options argument to override the IncomingMessage and ServerResponse constructed for each request. Pass this class as IncomingMessage and have convenient access to properties provided by url.parse and path.parse:

http.createServer({
    IncomingMessage: require("ParsedMessage")
}, (req, res) => {
    req.path       // url.parse(req.url).path
    req.pathname   // url.parse(req.url).pathname
    req.query      // querystring.parse(url.parse(req.url).query
    req.search     // url.parse(req.url).search
    req.hash       // url.parse(req.url).hash
    req.parsedUrl  // url.parse(req.url)
    req.parsedPath // path.parse(req.pathname)
    req.root       // path.parse(req.pathname).root
    req.dir        // path.parse(req.pathname).dir
    req.base       // path.parse(req.pathname).base
    req.ext        // path.parse(req.pathname).ext
    req.name       // path.parse(req.pathname).name
}))

Check out the source code, it's very simple. I cache the result of url.parse so it's only called once, and only once you use one of the shortcuts.

See also: Transflect, a Transform stream that can be piped from request to response: req.pipe(new Transflect).pipe(res)

See also: ServerFailSoft, an extension to ServerResponse that catches errors piped to it and closes the connection with an informative error.