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-data-exchanger

v1.0.1

Published

Data Exchanger for Electron

Downloads

3

Readme

Exchange data between the Main Process and Renderers (EXPERIMENTAL).


Installation

npm install electron-data-exchanger

The code below goes into your "index.html". It is only necessary if you want to avoid having passing the full path to the library during the ESM import.

    <script type="importmap">
        {
          "imports": {
            "electron-data-exchanger": "../node_modules/electron-data-exchanger/esm/index.mjs"
          }
        }
    </script>

Usage

MAIN PROCESS

    // We use the CommonJs format in main 
    const MainDataExchanger = require("electron-data-exchanger").MainDataExchanger;
    
    const dataExchanger = new MainDataExchanger()
    await dataExchanger.init(mainWindow)

    // Monitor RENDERER messages 
    dataExchanger.addListener(UserChannelIdentifier, function (data)
    {
        return {MainResponse: "Main___Response", youSent: data}
    })

    // Send message to the Renderer
    await dataExchanger.sendMessage("my-channel", {hi: "Message from MAIN"})

PRELOAD

    const proxyExchanger = require("electron-data-exchanger").ProxyExchanger;

    const dataExchanger = new ProxyExchanger();

    // We must pass all the channels
    dataExchanger.enableProxy(["my-channel"])

RENDERER

    // We use the ESM format in the view
    import {DomDataExchanger} from "electron-data-exchanger";

    // Initialise Data Exchangers
    const dataExchanger = new DomDataExchanger()
    await dataExchanger.init()
    
    // Monitor MAIN PROCESS messages 
    await dataExchanger.addListener(UserChannelIdentifier, function (data)
    {
        return {RendererResponse: "***", originalCaller: JSON.stringify(data)};
    });
    
    // Send a message to main
    const response = await dataExchanger.sendMessage("my-channel", {hello: "Message from RENDERER"}, true);