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

dpd-express2

v0.0.2

Published

run express as a dpd resource

Downloads

5

Readme

dpd-express

use express as a dpd resource

install

In your project root, run:

mkdir node_modules
npm install dpd-express

events

There is only 1 event right now: init. Create it in the dashboard or include a folder like this (/my-project is the root of the app, created with dpd create my-project):

/my-project
 /resources
  /express
   /init.js

Init is run when the resource is loaded. Inside init.js you get app which is a running express app. Handle anything like a normal express app:

app.get('/foo', function(req, res) {
  res.send('bar');
});

or middleware

app.use(function(req, res, next) {
  req.called = 'my middleware';
  next();
});

In other resources, this will be available as ctx.req.called.

You also get access to the dpd object, bound to the current request.

Render some todos:

app.get('/foo', function(req, res) {
  req.dpd.todos.get(function(todos) {
    res.render('index.ejs', {todos: todos})
  });
});

The request also comes with the me object if it exists.

app.get('/me', function(req, res) {
  res.send(req.me);
});

You can require() modules. They must be installed at the root of your project (/my-project/node_modules).