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 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-source-debugger

v1.1.4

Published

A tool for quickly setting up the environment of debugging React source code.

Downloads

207

Readme

English简体中文

react-source-debugger

A tool for quickly setting up the environment of debugging React source code.

Install

npm i -g react-source-debugger
# or
yarn global add react-source-debugger
# or
pnpm add -g react-source-debugger

Usage

Simplest usage, only 3 steps:

rsd create my-react-debug-app
cd my-react-debug-app
rsd init

Now, we have react(React source code directory)、test-demo(test project) and rsd.code-workspace(vscode workspace file) under my-react-debug-app.

And then, we can start debugging by doing these:

  1. open rsd.code-workspace with vscode;
  2. start dev in test-demo;
  3. launch debug within vscode Run and Debug module.

Configuration

rsd init automatically finds configuartion file(rsd.config.{js,mjs,cjs,json}) from current directory. If not found, will use default configuration.

You can manually specify configuration:

rsd init --config /path/to/rsd.config.js

Options

export default {
  react: {
    dir: '/path/to/react/source/code/',
    version: '18.2.0',
  },
  testProject: {
    dir: '/path/to/test/project/',
    scaffold: 'vite',
    useTs: true,
    mode: 'development',
    devPort: 3000,
  },
};

react.dir

source code directory of React, default where rsd init runs.

react.version

version of React, default 18.2.0. Only supports partial versions, will automatically match version with same major.

supports:

  • 16.14.0
  • 17.0.2
  • 18.2.0

testProject.dir

directory of test project, default directory where rsd init runs。If manually specify this option, other options under testProject are ineffective, maybe yiou should adjust your code to ensure you can debug correctly.

testProject.scaffold

scaffold of test project, default vite. Supports:

  • vite
  • create-react-app

testProject.useTs

use ts or not, default true.

testProject.mode

development mode, decides whether the logic of React __Dev__ executes or not,default development. Supports:

  • development
  • production

testProject.devPort

port of dev server and vscode debug attaches to, default 3000

Build React source

If versions of React that react-source-debugger provides can't satisfy you, you can build it manually.

Install dependencies

yarn install --frozen-lockfile

Installation in Apple M1 machine would throw error, solution see here.

Build

yarn build

Author

Javen Leung

License

MIT