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

create-cloudinary-react

v1.0.0-beta.23

Published

Scaffold a Cloudinary React + Vite + TypeScript project with interactive setup

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

const-cloudinaryconst-cloudinaryasi-cloudinaryasi-cloudinary

Keywords

cloudinaryreactvitetypescriptscaffold

Readme

create-cloudinary-react

npm version License: MIT PRs Welcome

The fastest way to start building with Cloudinary and React.

Scaffold a modern, production-ready Cloudinary application with React 19, Vite 6, and TypeScript 5. Features interactive setup, automatic environment configuration, and built-in AI coding assistance.

  • Node.js — use a current LTS release. The generated app lists supported versions under engines in its package.json.
  • A Cloudinary account (free tier available)

Beta Release - This is a beta version. We welcome feedback and bug reports!

Part of the Cloudinary Developers organization.

Build with Cloudinary!

📽️ Demo

Watch the demo

🎬 Features

  • 🚀 Modern Stack: React 19 + Vite 6 + TypeScript 5.7
  • 📦 Cloudinary SDKs: Pre-configured @cloudinary/react
  • 🤖 AI-First: Auto-generates configuration for Cursor, GitHub Copilot, and Claude
  • 🛠️ Best Practices: ESLint 9 + TypeScript-ESLint, strict type checking
  • ⚡ Interactive Setup: Validates your cloud name and configures .env automatically
  • 🎨 Typed Components: Includes a fully typed Upload Widget component
  • 🔌 MCP Support: Built-in Model Context Protocol configuration for advanced AI integrations

🚀 Quick Start

Use a current Node.js LTS release. If installs fail, match the engines range in the generated project’s package.json.

npx create-cloudinary-react

(No installation required)

The CLI will guide you through:

  1. Project Name: naming your new folder
  2. Cloud Name: entering your Cloudinary cloud name
  3. Upload Preset (Optional): handling unsigned uploads
  4. AI Assistant: generating custom rules for your tool of choice (Cursor, VS Code, etc.)

🛠️ What's Included

Your new project comes with:

  • src/: specialized for Cloudinary workflows
  • src/components/UploadWidget.tsx: A ready-to-use, typed upload component
  • .env: Pre-filled with your Cloud Name (and Upload Preset if provided)
  • README.md: Custom instructions for your specific project
  • AI Configuration:
    • .cursorrules / .cursor/mcp.json (for Cursor)
    • .github/copilot-instructions.md (for Copilot)
    • .claude / claude.md (for Claude)

🤖 AI Assistant Support

We believe AI is the future of development. This starter kit doesn't just give you code; it gives your AI context.

During setup, select your AI tool to generate Context Rules. These rules teach your AI:

  • How to construct Cloudinary transformation URLs correctly
  • How to use the @cloudinary/react SDK components
  • Common pitfalls to avoid (like mixing up import paths)
  • How to handle upload widget events

Supported Tools:

  • ✅ Cursor (Rules + MCP)
  • ✅ GitHub Copilot (Instructions)
  • ✅ Claude (Project context + MCP)
  • ✅ Generic LLMs (System prompts provided)

📋 Prerequisites

  • Node.js — LTS recommended; exact ranges for the scaffolded app are in package.json → engines.
  • Cloudinary Account: Sign up for free if you haven't already.

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

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

⚙️ Development

This project uses Conventional Commits for version management and semantic-release for automated releases.

Release Process

Releases are triggered manually via GitHub Actions workflow. The workflow uses npm trusted publishing (OIDC) for secure package publishing. New versions are published to npm when the workflow runs without dry run.

Dry run (default): When you run the workflow, "Dry run only" is checked by default. This runs semantic-release in dry-run mode—no git push, no tags, no npm publish. Use this to verify the next version and release notes before doing a real release. To publish for real, run the workflow again and uncheck "Dry run only". Each real release creates a GitHub release, updates CHANGELOG, and publishes the new version to npm (when the version changes).

Commit Format

<type>(<scope>): <subject>

<body>

<footer>

Types:

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • refactor: Code refactoring
  • perf: Performance improvements
  • chore: Other changes

📄 License

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