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 🙏

© 2026 – Pkg Stats / Ryan Hefner

next-method

v1.0.1-canary

Published

<img alt="" src="https://badgen.net/bundlephobia/minzip/next-method"> <br />

Readme

🕵🏻‍♂️ Next Method

next-method's goal is to make it easier to interact with Next's API routes by providing a wrapper around the request method. A simplistic, focused, and minimal interface.

Contents

Installation

Install using either NPM, Yarn, or a package manager of your choosing.

npm i next-method
# or
yarn add next-method

Usage

next-method is designed to be used within Next's API routes. After creating yourself an API endpoint you can then start working with it.

const m = require('next-method')

module.exports = (
  m.get((req, res) => {
    res.send('Hello, world!')
  })
)

In this minimal example we're accepting GET requests to our endpoint. Once the endpoint is hit we either send the expected GET response or we throw an exception.

Middleware

Adding middleware to any method is simple by making use of the use function, or the fact that methods can contain multiple handlers.

const m = require('next-method')

module.exports = (
  m
    .use((req, res, next) => {
      // Check for user authentication
      if (user === null) {
        return res.status(401).end()
      }

      return next()
    })
    .post((req, res) => {

      // Create object
      storeObject()

      res.status(201)
    })
    .get((req, res) => {

      // Get object details
      const details = {}

      res.json(details)
    })
)

// or

module.exports = (
  m
    .post([
      (req, res, next) => {
        // Verify post data
        if (data === 'bad') {
          return res.status(422).json({ errors: 'Bad data provided' })
        }

        return next()
      },
      (req, res) => {

        // Create object
        storeObject()

        res.status(201)
      }
    ])
    .get((req, res) => {

      // Get object details
      const details = {}

      res.json(details)
    })
)

In the examples above we make use of the next function that is provided as the third argument. This tells next-method to process the next handler.

Methods

next-method supports all HTTP methods that the user is expected to come across such as:

  • get
  • post
  • patch
  • put
  • delete

Each of these methods accept multiple handlers so can be processed in stages.

Catching missing methods

When a request has been made and the method is not defined, such as in the example below: put, an exception will be thrown.

There are many ways to catch and handle the exception, but we provide a custom error object that provides the: request, response, and method.

const m = require('next-method')

const authenticated = require('~/middleware/authenticated')
const action = require('~/actions/user')

module.exports = (
  m
    .use(authenticated)
    .post(action.create)
    .patch(action.update)
    .delete(action.remove)
    .get(action.retrieve)
    .catch(({ res, method }) => {
      res.status(422).json({ error: `${method} is not supported` })
    })
)