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

nxa

v1.0.9

Published

Minimalistc, zero dependencies and configurable Next.js API handler with hook support that avoids pointless boilerplate

Downloads

23

Readme

This projects was used in my project before Next.js 12 added support for middlewares, I'll leave this here just for fun now 😂

About

The purpose of this package is to help me prototype faster without wasting time writing countless boilerplate for Next.js api handlers.

Comes with support for hooks (beforeResponse, afterResponse, onError) to help you validate, check authentication and whatever you need.

You can also use conventience method to have a single file handling multiple http methods thus allowing you to write RESTful routes easily.

Installation

npm i nxa

Usage

// pages/api/users/index.js
const nxa = require("nxa");

export default nxa({
  // if handler method found it will be used for every request
  handler: (req, res) => res.end("OK"),

  // if {get,post,put,patch,delete} named method found it will be routed here
  get(req, res) {
    return res.json({ ok: 1 })
    
  },

  put(req, res) {
    // convenience use res.json under the hood and sets content-type to json
    return { ok: 1 }
  },
  
  // catch-all errors in your handlers
  onError(req,res,error) {
    // handler error and return
    return { message: "youwhatbro" }
  },

  // Executed serially in order
  beforeResponse: [
    validate,
    checkJwt,
    (req, res) =>{
    // exit before method handlers or just return empty to follow
    return "OK"
    
  }],

  // Fires when res emits "finish" event
  afterResponse: (req, res) => {
    // send some metrics?
  }
})

If you don't want nxa to route methods to named functions you can use a generic handler and check method on your own

// pages/api/users/index.js
const nxa = require("nxa");
export default nxa({
  handler(req, res) {
    if (req.method === 'GET') // Do what you need
  }
})

Options

nxa(options): AsyncFunction

| field | description | | --- | --- | | handler| Universal handler for all request on the file | | {head,get,post,put,patch,delete} | Convenience method to route http methods | | beforeResponse | Array of functions to execute before handling response | | afterResponse | function to execute on response finish | | onError | function called when there is an error in an handler |

Contributing

Project is pretty simple and straight forward for what is my needs, but if you have any idea you're welcome.

This projects uses commitizen so be sure to use standard commit format or PR won't be accepted

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'feat(scope): some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

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

Contact

Simone Corsi - @im_simonecorsi