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

micro-dev

v3.1.0

Published

This command line interface provides a belt full of tools that make building microservices using [micro](https://github.com/vercel/micro) a breeze! It's only meant to be used in development, **not in production** (that's where [micro](https://github.com/v

Downloads

6,957

Readme

Micro (Dev) — Asynchronous HTTP microservices

This command line interface provides a belt full of tools that make building microservices using micro a breeze! It's only meant to be used in development, not in production (that's where micro comes in).

Features

  • Hot Reloading: When making changes to your code, the server will restart by itself
  • Logs: Incoming and outgoing requests will be logged to stdout
  • Beautiful JSON: When JSON bodies are logged, they're styled and prettified
  • Clipboard Support: The local address is pasted to the clipboard automatically
  • Port Selection: Automatic detection and use of an open port (if the specified one is in use)
  • Debug in Your Network: The network address shown in addition to local one
  • Duration Logs: Calculates and shows the duration for each request
  • Pretty Errors: Prettifies the Error object if any exceptions are thrown

Usage

Important: This tool is only meant to be used in development. In production, you should use micro, which is much lighter and faster (and also comes without the belt of tools used when developing microservices).

When preparing your development environment, firstly install micro-dev:

npm install --save-dev micro-dev

Note: You'll need at least Node.js v7.6.0 to run micro-dev.

Next, add a new script property below micro inside package.json:

"scripts": {
  "start": "micro",
  "dev": "micro-dev"
}

As the final step, start the development server like this:

npm run dev

Debugging

The package can be used in conjunction with the Node.js inspector like this:

"scripts": {
  "inspect": "node --inspect node_modules/.bin/micro-dev"
}

As the final step, start the development server like this:

npm run inspect

Contributing

  1. Fork this repository to your own GitHub account and then clone it to your local device
  2. Move into the directory of the clone: cd micro-dev
  3. Link it to the global module directory of Node.js: npm link

Inside the project where you want to test your clone of the package, you can now either use npm link micro-dev to link the cloned source to your project's local dependencies or run micro-dev right in your terminal.

Authors