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-ipc-server

v0.1.2

Published

An IPC server with an API similar to Express.js' for Electron

Downloads

5

Readme

electron-ipc-server

NPM

An IPC server with an API similar to Express' for Electron.

Handling IPC messages in Electron can be a pain if you are building an app with a very active communication between processes. Instead of reinventing the wheel electron-ipc-server aims to reduce the learning curve by reimplementing well known patterns such as those used for routing in Express on the server side and a fetch*-ish* API on the client side. Internally it' still using ipcRenderer and ipcMain so there's nothing magic going on.

Quick example

// In main process
const server = require('electron-ipc-server').createServer(app)

server.get('/users', (req, res) =>
{
    let users = // you get the users from your backend
    res.status(200).send(users)
})
// In render process
const client = require('electron-ipc-server').createClient()

client.get('/users')
.then(response =>
{
    console.log(`users`, response.body)
    // now go and do something with your list of users!
})

Installation

npm i electron-ipc-server --save

Features

What the client (renderer process) can do

  • Send requests to the main process and handle responses using Promises.
  • Use regular HTTP verbs like GET, POST, PUT and DELETE.
  • Still use regular events with client.on().

What the server (main process) can do

  • Respond to regular HTTP verbs like GET, POST, PUT and DELETE.
  • Use an API similar to what Express offers, with middleware, params, query-strings, and much more.
  • Broadcast messages (by definition, to all clients).

Documentation

TODO

  • [ ] Add guides to /docs
  • [ ] Add /examples

License

MIT