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-backend

v0.0.2

Published

This project is a backend server built for Next.js.

Downloads

5

Readme

next-api-backend

This project is a backend server built for Next.js.

Features

The server has the following features:

  • Middleware: The server supports the use of middleware, which are functions that are executed before the main route is handled. Middlewares can be defined with the defineMiddleware function, which takes a middleware or a list of middlewares, along with optional parameters and options.

  • Routes: Routes are defined with the defineRoute function, which takes a route function and an optional list of middlewares. This function returns a new function that handles the route and executes the middlewares.

  • Context: The server maintains a global context object, which can be accessed and modified with the getContext and setContext functions.

Use

To define a middleware, you can use the defineMiddleware function as follows:

const myMiddleware = defineMiddleware(
    (context) => {
        // Your code here
    },
    [param1, param2],
    { includes: ['route1', 'route2'], excludes: ['route3'], verbs: ['GET'] }
)

To define a route, you can use the defineRoute function as follows:

export const GET = defineRoute(
    (request, params) => {
        // Your code here
    },
    [myMiddleware]
)

To access the context object, you can use the getContext function as follows:

const value = getContext('key')

To modify the context object, you can use the setContext function as follows:

setContext('key', value)

Contribute

If you would like to contribute to this project, please fork the repository and submit a pull request with your changes.

License

This project is licensed under the terms of the MIT License.