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-react-debug

v1.0.2

Published

create debug react source code cli

Readme

create-react-debug Npm Version

Quick Overview

npm i -g create-react-debug
create-react-debug project-directory

If you haven't previously installed yarn, please install it using npm install -g yarn.

If you've previously installed create-react-debug globally via npm install -g create-react-debug, please uninstall the package using npm uninstall -g create-react-debug or yarn global remove create-react-debug to ensure always uses the latest version.

If you've previously linked react and react-dom , please unlink them using npm unlink react react-dom or yarn unlink react react-dom.

Install

npm i create-react-debug

Creating a debug react source code environment

This is based on react and create-react-app, so you need to fulfil the requirement of react and create-react-app。 For Example:

You’ll need to have Node 14.0.0 or later version on your local development machine (but it’s not required on the server). We recommend using the latest LTS version. You can use nvm (macOS/Linux) or nvm-windows to switch Node versions between different projects.

Use following methods to build a debug environment, this may take a while:

npm

create-react-debug test

It will create a directory called test inside the current folder. Inside that directory, it will generate the initial project structure and install the transitive dependencies:

test
├── README.md
├── package.json
├── public
│   ├── favicon.ico
│   ├── index.html
│   ├── logo192.png
│   ├── logo512.png
│   ├── manifest.json
│   └── robots.txt
├── src
│   ├── App.css
│   ├── App.js
│   ├── App.test.js
│   ├── index.css
│   ├── index.js
│   ├── logo.svg
│   └── react
│       └── build
│           └── node_modules
│               ├── react
│               └── react-dom 
├── tsconfig.json
└── yarn.lock

Once the installation is done, you can open your project folder:

cd test

React source code is placed inside src/react You can debug in src/react/build/node_module/react or src/react/build/node_module/react-dom to enjoy react source code

Inside the newly created project, you can run some built-in commands:

npm start or yarn start

Runs the app in development mode. Open http://localhost:3000 to view it in the browser.

Others

react create-react-app

TODO:

  1. handle project-directory already exist
  2. automatically install yarn
  3. add test