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-protocols

v1.0.4

Published

Manage file protocols in Electron

Downloads

33

Readme

electron-protocols

Linux Build Status Windows Build status Dependency Status devDependency Status

Manage file protocols in Electron

Install

npm install --save electron-protocols

Run the example:

npm start example

Usage

First register your protocol in main process before app.on('ready'):

main process

const protocols = require('electron-protocols');
protocols.register('app', protocols.basepath(app.getAppPath()));

Then you can use protocols.path to map your protocol to a file path:

renderer/main process

const protocols = require('electron-protocols');

// return the module in ${app.getAppPath()}/my/module.js
const myModule = require(protocols.path('app://my/module.js'));

Also, you are free to use protocol in html in renderer process:

  <img src="app://my/image.png" />
  <script src="app://my/script.js" />

FAQ

What is the benefit to register again in renderer process?

It will speed up the search of protocols.path by skip calling the remote (ipc-sync) functions.

API

Methods

protocols.register(protocol, fn)

  • protocol string
  • fn function

Register a protocol so that {@link Editor.url} can use it to convert an url to the filesystem path. The fn accept an url Object via url.parse

Example:

const {app} = require('electron');
const protocols = require('electron-protocols');
const path = require('path');

protocols.register('app', uri => {
  let base = app.getAppPath();
  if ( uri.pathname ) {
    return path.join( base, uri.host, uri.pathname );
  }
  return path.join( base, uri.host );
});

protocols.path(url)

  • url string

Convert a url by its protocol to a filesystem path. This function is useful when you try to get some internal file. You can use protocols.register to register and map your filesystem path to url.

Example:

// it will return "{your-app-path}/foobar/foobar.js"
protocols.path('app://foobar/foobar.js');

protocols.basepath(base)

  • base string

A function help you register protocol by base path you provide.

Example:

protocols.register('app', protocols.basepath(app.getAppPath()));

License

MIT © 2017 Johnny Wu