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

v1.2.2

Published

An HTTP router, reverse-proxy and process manager for composing Next.js microservices.

Downloads

22

Readme

Next Micro

npm version

An HTTP router, reverse-proxy and process manager for composing Next.js microservices.

Next Micro launches a reverse-proxy that becomes the entry point via which all underlying services are accessed. When a route is hit Next Micro will launch the responsible service automatically then, to help manage resources, close it down after a specified time to live (TTL).

The available routes for each Next.js service are determined by parsing the file system. Any additional routes can be specified directly in the configuration file, as can any supplementary non Next.js services.

View the docs

Getting Started

Given a monorepo containing multiple Next.js microservices the easiest way to get started is to install Next Micro in the root of the monorepo:

npm install next-micro -D

Add the following section to your package.json:

{
  "scripts": {
    "dev": "nextmicro dev",
  }
}

And run:

yarn dev

The proxy should now be up and running at http://127.0.0.1:3000.

When we make requests to this address traffic will be routed to the Next.js service that handles that route. If the service is not running it will be launched automatically.

View the full docs for details of how to configure further.