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

express-with-json

v0.0.6

Published

Express library which allows middleware functions to just return objects to send to client

Downloads

10

Readme

express-with-json

Add functions which return objects as middlewares to express.

Avoid calling res.json() catching errors and calling next in every json-returning middleware. Instead, why not just:

  • returning the object you want JSON-ed to the client or
  • throwing JsonErrorResponse to return JSON-ed error to the client or
  • throwing any other error to have next() called with it

Installation:

npm install express-with-json

Usage example:

import express from 'express';
import bodyParser from 'body-parser';
import fetch from 'node-fetch';
import withJson, { JsonErrorResponse } from 'express-with-json';

const app = withJson(express());
// app is a regular express instance just with a few extra methods

app.use(bodyParser.json());

app.get('/', (req, res) => res.send('Hello World!'));

app.getJson('/ok', () => {
  return { ok: true };
});
app.getJson('/fail', () => {
  throw new JsonErrorResponse({ ok: false }, { statusCode: 501 });
});
app.getJson('/fail2', () => {
  throw new Error('This error will cause next to be called');
});
app.postJson('/echo', (req, res) => {
  return req.body;
});
app.getJson('/async-demo', async () => {
  const response = await fetch('https://api.github.com/repos/ikatun/express-with-json');
  return await response.json();
});

const port = 3000;
app.listen(port, () => console.log(`Example app listening on port ${port}!`));