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.11

Published

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

Vulnerabilities

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

Links

Git

Maintainers

cloudinarycloudinary

Keywords

cloudinaryreactvitetypescriptboilerplatescaffold

Readme

create-cloudinary-react

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

Part of the Cloudinary Developers organization.

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

Prerequisites

Usage

npx create-cloudinary-react

The CLI will prompt you for:

  • Project name
  • Cloudinary cloud name (found in your dashboard)
  • Upload preset (optional - required for uploads, but transformations work without it)
  • AI coding assistant(s) you're using (Cursor, GitHub Copilot, Claude, etc.)
  • Whether to install dependencies
  • Whether to start dev server

Features

  • ✅ Interactive setup with validation
  • ✅ Pre-configured Cloudinary React SDK
  • ✅ TypeScript + Vite + React 19
  • ✅ Typed Upload Widget component
  • ✅ Environment variables with VITE_ prefix
  • ✅ Multi-tool AI assistant support (Cursor, GitHub Copilot, Claude, and more)
  • ✅ MCP configuration for Cloudinary integration
  • ✅ ESLint + TypeScript configured

AI Assistant Support

During setup, you'll be asked which AI coding assistant(s) you're using. The CLI will generate the appropriate configuration files:

  • ✅ Cursor → .cursorrules + .cursor/mcp.json (if selected)
  • ✅ GitHub Copilot → .github/copilot-instructions.md
  • ✅ Claude Code / Claude Desktop → .claude, claude.md + .cursor/mcp.json (if selected)
  • ✅ Generic AI tools → AI_INSTRUCTIONS.md, PROMPT.md

MCP Configuration: The .cursor/mcp.json file is automatically generated if you select Cursor or Claude, as it works with both tools.

These rules help AI assistants understand Cloudinary React SDK patterns, common errors, and best practices. The generated app also includes an "AI Prompts" section with ready-to-use suggestions for your AI assistant.

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