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

@bugsnag/plugin-electron-ipc

v8.0.0

Published

@bugsnag/electron plugin to create the IPC layer between main and renderer processes

Downloads

7,427

Readme

@bugsnag/plugin-electron-ipc

This plugin implements the IPC layer which is used to synchronise data between the main and renderer processes.

The plugin itself (electron-ipc.js) runs in the main Electron process and does the following things:

  • Sets up listeners in the main process that renderers can use to
    1. retrieve config with which to start a client
    2. propagate state changes during the lifecycle of a client
    3. mange sessions and send events
  • Injects a preload script to every new renderer process, ensuring the IPC interface is available in browser windows as a global variable
  • Listens for changes to client state in the main process (emitted by @bugsnag/plugin-state-sync) and propagates them to all renderer processes

The interface exposed to renderers is defined in bugsnag-ipc-renderer.js, and the class used to route events to relevant actions in the main process is defined in bugsnag-ipc-main.js.

All data send over the IPC layer is serialised using @bugsnag/safe-json-stringify for greater flexibility. Electron's default serialialisation method will throw if any complex objects are referenced, or there are any circular structures. To deserialise it is simply JSON.parse()d.

License

This package is free software released under the MIT License. See LICENSE.txt for details.