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

npm2dock

v1.0.0

Published

Convert any npm package into a runnable container

Downloads

16

Readme

npm2dock

Convert any npm package into a runnable container

Usage

$ npm2dock micro-sleep

Downloads the latest stable version (npm install behaviour) of the micro-sleep package and creates a docker image named micro-sleep with a tag corresponding to the version of the resolved package.

$ npm2dock [email protected]

Does the same thing but resolves to the 1.0.1 version of the package (npm install behaviour) This then generates the micro-sleep:1.0.1 image on your docker.

Run it

Once you've generated your images, they can be run anywhere like this for example

$ docker run -d -p 3000:3000 micro-sleep:1.0.0

Conventions

npm2dock makes 3 main assumptions about the structure of the packages it pulls from npm:

  • it has an npm start script configured
  • it starts a server on at least one of these ports: 3000 8000 8080 8443
  • it only needs a node.js runtime to run.

Additionnally it is strongly recommended that configuration is made via ENV variables

If the package you want to run follows these, then life will be a breeze anyway.

Dependencies

the npm2dock executable itself is a bash script relying on the presence of Docker on the host.

  • bash
  • docker
  • npm

What does it actually do?

Almost nothing. The source code is shorter than this README.

Notes

npm2dock currently uses the mhart/alpine-node image as a base for its reasonable size.

License

MIT

Copyright (c) 2016 Florent Jaby

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.