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

@billyen2012/next-api-router

v1.11.3

Published

A next.js api router that feels like express.js

Downloads

59

Readme

Home Page

  • Please use home page for all api references. It aslo has more info like how to setup Graphql, Swagger, supported express.js middlewares, etc.

Installation

npm i @billyen2012/next-api-router

or for yarn

yarn add @billyen2012/next-api-router

Quick Start

under the /app dir, create a folder structure as shown below

app/
└── api/
    └── [...]/
        └── route.js
  • The [...] means to catch all the the request. This is required since NextApiRouter will create a separete route table to match the request url.

Then in the route.js, add the following

import NextApiRouter from "@billyen2012/next-api-router";

const app = NextApiRouter({
  timeout: 20 * 1000,
  apiFolderPath: "/api", // '/api' will be the default
  ejsFolderPath: "/src/app/views", // need include all folder encounter from the route (there is no default value). No need to set this up if you are not using ejs
});

app.get("/hello", (req, res, next) => {
  res.send("Hello");
});

const handler = app.handler();
export const dynamic = "force-dynamic";
export const GET = handler;
export const POST = handler;
export const PUT = handler;
export const DELETE = handler;

The Base Route Problem

The example shown in the quick start section will not process the base route such as app.get("/"). If you do need the base route to be open, you can do the following.

app/
└── api/
    ├── [...]/
    │   └── route.js
    └── route.js

And then have your const export app = NextApiRouter() created in some other folder or file and then import them to both route.js