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

docker-build-run-push

v3.0.0

Published

npm scripts to automate working with docker images.

Downloads

567

Readme

docker-build-run-push

npm scripts to automate docker images.

An easy way to excute the typical sequence of building, running and pushing a docker image out of a node project to a private docker repo, or the public docker hub.

Uses the name and version number from package.json to keep your docker image name and version aligned.

Usage

in your project, execute

npm install docker-build-run-push --save

If you are pushing to a private docker repo, add the following to your package.json

  "docker-registry": "docker.your-private.com",

Or if you are pushing to the public docker hub, add the following to your package.json

"docker-user": "ryanramage".

Add some scripts that look like this. You might adjust to your liking

  "scripts": {
	    "docker-build": "rm -rf node_modules && npm i --production && docker-build",
	    "docker-run": "docker-run",
	    "docker-push": "docker-push",
  },

Now in your project, when you are ready to make a new image, bump your version number in package.json.

To build a local docker image quickly, for running later

npm run docker-build

Run the local docker image just built

npm run docker-run

Push the docker image to the docker-registry specified in your package.json

npm run docker-push

docker-run arguments

It's common to have to pass arguments when running a docker. The '+' character to split the arguments for the docker command.

Here are some example of what they mean

Run a different command in the docker image then the CMD specified

npm run docker-run — node ./bin/cli.js

Pass a port and an env file as arguments.

npm run docker-run -- -p 3000:3000 --env-file .env + 

Start an interactive terminal

npm run docker-run -- -i -t + /bin/bash