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

wp-env-port-stamp

v2.3.0

Published

Add ports with Unix timestamp.

Downloads

1

Readme

wp-env-port-stamp

npm version

TL;DR: wp-env-port-stamp is a npm package who generates an .wp-env.json file with custom ports for your wp-env environment.

Background

If you are working with different Docker environments at the same time, you need to manage the ports. wp-env uses port 8888 by default. If this port is already used by another project, you have a problem. But the solution is simple: just change the ports.

wp-env-port-stamp generates a new port address - more or less - randomly. When the package is called, the following happens:

  • It checks if a file .wp-env.json exists in the executing directory.
  • If yes, only the two ports are set or changed. The other values remain untouched.
  • If no, a new file is created.

Port number generation

The port numbers (wp-env configuration needs 2 ports) are generated from the current JavaScript date - the time in milliseconds since the ECMAScript epoch. The last digits of this time are used as port number. This number is somewhere between 1 and 65535. There is also a filter that prevents commonly used port numbers (e.g. 8888) from being used. Last but not least, a check is made to ensure that the generated port numbers are not already in use at the time of generation.

My solution may not be perfect, but it is good enough for daily local web development with a handful of Docker instances :-)

Install/Remove

Install the package globally on your local computer:

npm install -g wp-env-port-stamp

To remove the package:

npm uninstall -g wp-env-port-stamp

Usage

  1. Go in your local dev environment to your plugin, theme or block root directory or wherever you want to start wp-env.
  2. Call the package: wp-env-port-stamp
  3. The file is generated. You can start now with wp-env

Normally you only need to call the package for the first time in a new project. Later just start directly wp-env.