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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@debugger_supreme/dockerizeit

v1.0.0-beta.1

Published

CLI tool to generate Docker and Docker Compose files for various project types

Downloads

6

Readme

dockerizeit

🐳 CLI tool to automatically generate Docker and Docker Compose files for your projects

⚠️ This package is currently in beta. Use with caution in production environments.

Features

  • 🔍 Automatic detection of project structure and frameworks
  • 🛠️ Support for multiple frameworks:
    • Frontend: React, Vue, Angular, Next.js, Svelte
    • Backend: Express, NestJS, Koa, Fastify, Django, Flask
  • 📦 ORM support: Prisma, Sequelize, TypeORM, Knex, Mongoose
  • 🗄️ Database support: PostgreSQL, MongoDB, MySQL, MariaDB, SQLite
  • 🔌 Additional services: Redis, RabbitMQ, Elasticsearch, Memcached
  • 🚀 Multi-stage builds for optimal container size
  • ⚡ Automatic detection of package managers (npm, yarn, pnpm)
  • 🔒 Environment variable handling
  • 📝 Nginx configuration for static builds

Installation

npm install -g @debugger_supreme/dockerizeit@beta

Usage

Navigate to your project directory and run:

dockerizeit

The CLI will:

  1. Detect your project structure
  2. Identify frameworks and dependencies
  3. Generate appropriate Dockerfiles
  4. Create a docker-compose.yml with all required services

Options

dockerizeit [options]

Options:
  -V, --version              output the version number
  -p, --path <path>         path to project directory (default: current directory)
  -f, --force               overwrite existing Docker files
  --node-version <version>  specify Node.js version (default: "20")
  --python-version <version> specify Python version (default: "3.11")
  -h, --help               display help for command

Examples

Basic usage:

cd your-project
dockerizeit

Specify project path:

dockerizeit -p /path/to/project

Force overwrite existing files:

dockerizeit -f

Specify Node.js and Python versions:

dockerizeit --node-version 18 --python-version 3.10

Project Structure Support

The tool supports various project structures:

  1. Monorepo with frontend and backend:
project/
├── frontend/
│   ├── package.json
│   └── src/
└── backend/
    ├── package.json
    └── src/
  1. Backend with frontend subdirectory:
project/
├── frontend/
│   ├── package.json
│   └── src/
├── src/
├── package.json
└── ...
  1. Single package:
project/
├── package.json
├── src/
└── ...

Contributing

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.