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

electron-inspector

v0.1.4

Published

Debugger UI for the main Electron process

Downloads

6

Readme

electron-inspector

Debugger UI for the main Electron process

Overview

This package wraps node-inspector, which can be used to debug JavaScript code running in the main Electron process. Getting node-inspector running can require somewhere between a little and a lot of effort depending on the Electron version you wish to debug. The goal of electron-inspector is to get node-inspector running with minimum effort on your part.

Prerequisites

Quick Start

electron-inspector should be installed as a local dev dependency of your Electron app:

npm install electron-inspector --save-dev

The easiest way to run the inspector in a cross-platform manner is to add an NPM script to your package.json, for example:

"scripts": {
  "inspect-main": "electron-inspector"
}

Then run the inspect-main script on the command line with:

npm run inspect-main

Alternatively, if you don't want to mess with your package.json you can directly execute electron-inspector (macOS / Linux), or .\\node_modules\\.bin\\electron-inspector (Windows).

On startup electron-inspector will check for compatibility of the native modules in node-inspector with the Electron version you wish to debug, if the compatibility check fails and electron-rebuild is installed then the native modules will be automatically rebuilt. You can disable auto-rebuild using the --no-auto-rebuild command line option.

When electron-inspector finally gets node-inspector running you will see a URL printed to the console window. For example:

Visit http://127.0.0.1:8080/?port=5858 to start debugging.

You can then start Electron in debug mode and open the given URL in your browser.

Configuration

node-inspector can be configured in multiple ways, electron-inspector will pass through most of the supported command line options.

Command Line Options

electron-inspector accepts most of the commandline options node-inspector does:

License

MIT