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

genit-all

v1.0.1

Published

AI-powered file generator for TypeScript projects - generates Dockerfiles, README, .gitignore and more

Readme

genit-all

npm version License: MIT TypeScript

genit-all is an AI-powered command-line interface (CLI) tool designed to streamline the initial setup of TypeScript projects by generating essential project files like Dockerfiles, READMEs, .gitignore, and more, using the power of Google's Gemini AI.

✨ Features

  • AI-Powered File Generation: Leverage the Google Gemini AI model to intelligently generate project configuration files.
  • Dynamic Dockerfile Creation: Automatically create optimized Dockerfiles tailored to your project's needs.
  • Comprehensive README Generation: Generate professional and detailed README.md files, saving you time on documentation.
  • Smart .gitignore Generation: Create effective .gitignore files to keep your repository clean and focused.
  • Interactive CLI Experience: Enjoy a user-friendly and guided experience through interactive prompts.
  • TypeScript First: Built with TypeScript for type safety, maintainability, and scalability.
  • Extensible: Designed to be easily extended for generating other project files in the future.

🚀 Installation

To use genit-all, you need Node.js (v18 or higher recommended) and npm or Yarn installed.

Install genit-all globally via npm:

npm install -g genit-all

Or using Yarn:

yarn global add genit-all

⚙️ Configuration

genit-all requires a Google Gemini API key to interact with the AI model.

  1. Obtain a Google Gemini API Key:

  2. Set up your Environment Variable: Create a .env file in the directory where you plan to run genit-all (e.g., your project root) and add your API key:

    GOOGLE_API_KEY=YOUR_GEMINI_API_KEY_HERE

    Important: Never commit your .env file or API keys to version control. Make sure .env is included in your .gitignore.

💡 Usage

Once installed and configured with your API key, you can run genit-all from your terminal:

genit-all

The CLI will then guide you through an interactive process, asking questions to understand your project and what files you want to generate.

Example: Generating a Dockerfile

$ genit-all
? Welcome to genit-all! What would you like to generate today? (Use arrow keys)
❯ Dockerfile
  README.md
  .gitignore
  ...

Follow the prompts to specify your project type, language, and other relevant details, and genit-all will generate the file for you.

📦 Project Structure

.
├── dist/                      # Compiled JavaScript output
├── src/                       # Source code directory
│   ├── cli/
│   │   └── main.ts            # Main entry point for the CLI
│   ├── types/
│   │   └── index.ts           # TypeScript type definitions and interfaces
│   └── utils/
│       ├── ai.util.ts         # Utility functions for AI model interaction
│       ├── helpers.util.ts    # General helper utility functions
│       └── ui.util.ts         # Utility functions for user interface and prompts
├── .gitignore                 # Files and directories ignored by Git
├── .npmignore                 # Files and directories ignored by npm when publishing
├── package.json               # Project metadata, dependencies, and scripts
├── package-lock.json          # Dependency tree lock file
└── tsconfig.json              # TypeScript compiler configuration

📜 Available Scripts

In your project's package.json, the following scripts are defined for development and building:

  • npm run dev: Runs the CLI directly from the TypeScript source files using ts-node. Ideal for local development and testing changes without a full build.

    npm run dev
  • npm run build: Compiles the TypeScript source code (src/) into JavaScript and places the output in the dist/ directory. This command must be run before npm start or publishing.

    npm run build
  • npm start: Executes the compiled CLI from the dist/ directory. This is how the tool runs in a production-like environment after building.

    npm start
  • npm run prepublishOnly: A lifecycle script that automatically runs npm run build before the package is published to npm. This ensures that only compiled and ready-to-use code is published.

  • npm test: Currently a placeholder script. Future updates will include comprehensive tests here.

🙌 Contributing

We welcome contributions to genit-all! If you'd like to contribute, please follow these steps:

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

Please ensure your code adheres to the existing style and conventions.

📄 License

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

👤 Author

King Faithful