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

react-gdb

v0.1.0

Published

GDB frontend in react.js

Readme

GDB Frontend in React

The goal of this project is to provide a GUI for GDB in the browser so that other developers can use it to easily and intuitively debug projects running in a cloud environment.

Example

Tickets Yep, there's not much beatiful UI out here right now. But at least it works :)

Install

$ npm install react-gdb

:warning: Note, that react-gdb is still under development. Use to your own risk!

Usage

import React from 'react'
import { render } from 'react-dom'
import ReactGDB from 'react-gdb'

render(<ReactGDB {...props} />, document.getElementById('gdb'))

API

|Prop|Description| |-----|----------| |process|Object representing the GDB/MI process| |process.stdin|Node.js Writable stream| |process.stdout|Node.js Readable stream| |process.stderr|Node.js Readable stream| |sourceProvider|Responsible for fetching the sources| |sourceProvider.filter|Python RegExp, files that don't match it will be ignored| |sourceProvider.fetch|Function that accepts the full path to a file and returns Promise that resolves with the source code| |inferiorProvider|Node.js EventEmitter with the fork event that emits pids, then these processes are attached to debugging session (is needed for debugging multiple processes)| |attachOnFork|Flag that disables detach-on-fork GDB/MI option (all fork'ed and vfork'ed processes will be attached automatically)| |objfileFilter|react-gdb refreshes source files list every time new objfile is added (e.g. new target or execl call), but in order to avoid unnecessary refreshes it's recommended to provide the RegExp that filters new objfiles|

Playing with examples

$ npm install
$ npm run docker-pull
$ npm run docker-run
$ npm start
$ npm run docker-rm

This will pull the image from Docker Hub, launch it in the new container, run WebSocket server that passes process streams to the client-side and build the example application. Open http://localhost:8080/index.html and play along. If you want to change the example that is being debugged, change the let example = '<example>' line in the client.jsx, save it and webpack will do all the rest.

TODO

  • Split components into smaller ones
  • Style components, draw some nice UI
  • Enable custom theming for CSS Modules
  • Tests, tests, tests...