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

minihost

v0.4.1

Published

dev utility

Downloads

33

Readme

minihost Build Status npm version

When working with many dev servers, you have to increment and remember ports (e.g. http://localhost:3000, http://localhost:4000, ...).

With minihost, you don't have to think about that.

Works on Windows, Linux and OS X.

Usage

Install:

npm install -g minihost

Prefix your commands with h:

~/one$ h -- nodemon
~/two$ h -- npm start

You can then view your running servers on http://localhost:2000 and access them locally on http://<name>*:2000 using any host that resolves to 127.0.0.1.

For example:

# Using dnsmasq and a local .dev domain
# Or /etc/hosts
http://one.dev:2000
http://two.dev:2000

Public wildcard domain names that resolves to 127.0.0.1 are also supported and can be used without any system configuration:

# See til.io
http://one.til.io:2000
http://two.til.io:2000

# See xip.io
http://one.127.0.0.1.xip.io:2000
http://two.127.0.0.1.xip.io:2000

To set a custom name, add -n:

~/one$ h -n app -- nodemon

To set a custom port environment variable name (instead of default PORT), add it after colon in custom name:

~/one$ h -n app:APP_PORT -- nodemon

To enable multiple names and ports repeat -n option:

~/one$ h -n app1:APP1_PORT -n app2:APP_PORT1 -- nodemon

If custom env variable names for ports not defined, PORT_0, PORT_1, ... will be used.

To change the port minihost listens to, run:

echo 8000 > ~/.minihost

Supporting minihost

For minihost to work, your server need to listen on the PORT environment variable.

From your code:

// KO
app.listen(3000);

// OK
app.listen(process.env.PORT || 3000);

Or from the command-line:

h -- 'cmd -p $PORT'  # Linux, OS X
h -- "cmd -p %PORT%" # Windows

License

MIT - Typicode