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

next-api-mw

v0.3.1

Published

Compose middleware for Next.js API routes like React Hooks

Downloads

11

Readme

license-shield linkedin-shield size-url size-url2 npm-v gh-shield

About The Project

Consuming API middleware should be as easy as using hooks in React. When using next-api-mw you can abstract common logic like auth or verifying query params into a middleware that can be used inside of an API route.

When calling middleware inside your route, that middleware may either return a promise, or handle the request itself thereby stopping the rest of the handler and or middleware from running.

Getting Started

npm i next-api-mw
import { HandlerFactory, createMiddleware } from 'next-api-mw'

// create one handler factory, then export it so you can create handlers for all your routes
export const handlerFactory = new HandlerFactory({
  handleError: async ({req,res,e}) => {
    res.status(500).json({ msg: 'server error' })
  },
  logger: async ({req,res,e}) => {

  },
  rootMiddleware: async ({req, res, end}) => {
    if(req.url.includes('token')){
      res.status(200).json({msg: 'token-accepted'})
      end()
    }
  }
})

// middleware can be consumed in as many routes as you want
// you can even use one middleware inside of another
const usingFooQS = createMiddleware(async ({req, res, end}) => {
  const { foo } = req.query

  if (!foo || typeof foo !== 'string') {
    res.status(400).json({ msg: 'invalid foo' })
    // the res will be sent and the remainder of this handler and the next middleware will not be evaluated
    end()
  }

  return foo as string
})

// default export a handler in any file under page/api
export default handlerFactory.getHandler(async ({req, res, end}) => {
  // you may consume middleware inside of get handler
  const foo = await usingFooQS({req, res})
  res.status(200).json({ foo })
  end()
})

Roadmap

See the open issues for a list of proposed features (and known issues).

Contributing

I'm open to all community contributions! If you'd like to contribute in any way

Run The Tests

Tests are E2E with Cypress. To get started run these commands:

npm i
npm run dev
npm run test

License

Distributed under the MIT License. See LICENSE for more information.

Contact

Teague Stockwell - LinkedIn