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

@a1motion/electron-kit

v1.2.2

Published

Opinionated electron build tool.

Downloads

9

Readme

electron-kit

Opinionated electron build tool.

Heavily inspired by desktop/desktop and react-scripts

File Structure

This project has a few expectations of the file structured used by your app.

Both JavaScript and TypeScript with React is supported everywhere, but we'll use TypeScript in the examples.

Required file structure:

preload.ts is required but can be empty if its not needed.

All files in static folder will be copied over, and index.html will be used as your entry point to your React app.

.electron-kit/
  config.js
src/
  main/
    index.ts
  renderer/
    index.tsx
    preload.ts
  static/
    index.html

Configuration

TODO

Compile Time Variables

| Name | Value | | ---------------- | ------------------------------------------------------------------------------ | | VERSION | The version of your app, as specified in your package.json. | | PROCESS_KIND | Used internally, but is set to main or renderer, depending on the process. |

Runtime API

| Warning: Electron will be deprecating shared globals between processes, you should instead looking to converting your API to use IPC methods instead. | | --- |

Electron allows you to import dependencies even inside the renderer, and use this as if you were in the main process. However this tool does not keep node_modules/ in the final build so this method will longer work.

Instead in your main process you should register your modules to work in the renderer process.

// main
import kit from "electron-kit";
import Store from "electron-store";

const store = new Store();

kit.registerModule("store", store);

// renderer
import kit from "electron-kit";
const store = kit.importModule("store");

Use IPC methods (recommended)

// main
import { ipcMain } from "electron";
import Store from "electron-store";

ipcMain.handle(`store-get`, (e, key, defaultValue) => {
  return store.get(key, defaultValue);
});

ipcMain.handle(`store-set`, (e, key, val) => {
  return store.set(key, val);
});

ipcMain.handle(`store-delete`, (e, key) => {
  return store.delete(key);
});

// renderer
import { ipcRenderer } from "electron";

const store = {
  get(key: string, defaultValue?: string) {
    return ipcRenderer.invoke(`store-get`, key, defaultValue);
  },
  set<T>(key: string, val: T) {
    return ipcRenderer.invoke(`store-set`, key, val);
  },
  delete(key: string) {
    return ipcRenderer.invoke(`store-delete`, key);
  },
};

Typescript

electron-kit provides many runtime and compile time utilities. Typescript should pick up the Runtime API by itself. However to get type access to the compile time variables add a index.d.ts file to the root of your app and add the following:

/// <reference types="@a1motion/electron-kit/managed" />