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 🙏

© 2025 – Pkg Stats / Ryan Hefner

envented

v0.0.11

Published

Evented node.js server framework

Downloads

9

Readme

#envented ##Evented node.js server framework ##Install

$ npm install envented

##Run tests

$ npm test

or

$ make test

##Why Node.js has a lot of events. The process object has events. HTTP servers have events. Streams have events. Higher-level modules have events. However, you can't really write a web app with events. Node http servers emit events, but they don't emit events based on the type of request. For example

var server = http.createServer();
server.on('request', function(req, res){
	// do stuff
});

Do you do that? Probably not, you probably just do this:

var server = http.createServer(function(req, res){
	// do stuff
});

Now, those two methods of creating a server are the same. Which means building an actual server out of one or the other is also the same.

##Get to the point

envented lets you do this:

var envented = require('envented');

var server = envented.Server() // this accepts an onRequest callback

server.use(server.router); // server is a connect.Server instance. YOU MUST USE THE ROUTER

server.on('get::/', function(req, res){
	res.end("Hi");
});

server.on('post::/form', function(req, res){
	// handle post data
});

The event namespacing is courtesy of EventEmitter2. All your favorite connect middleware is inside of envented.