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

v0.0.2

Published

electron-renderify

Downloads

276

Readme



Install

npm install electron-renderify

Usage

This module is to be used as a browserify transform.

Depending on what is in your bundle, and how you are setting up Electron, you may need to apply some or all of the following browserify settings:

{
  builtins: [],
  commonDir: false,
  detectGlobals: false,
  ignoreMissing: true,
  insertGlobalVars: 'global',
  browserField: false
}

The best place to apply the settings is in your package.json. That way they will take effect with either CLI or JS api use.

CLI

browserify -t electron-renderify sample.js > bundle.js

JS

var browserify = require('browserify')
var renderify = require('electron-renderify')

var path = require('path')

browserify()
  .transform(renderify)
  .add(path.join(__dirname, 'sample.js'))
  .bundle()
  .pipe(process.stdout)

Options

You can modify the behaviour of electron-renderify by passing options to the transform, like this:

browserify()
  .transform(renderify, opts)

The following options are available:

opts.windowRequire [Array[String]]

An array of strings, each of which specifies a module that should use window.require instead of plain require. This might be required for any native modules (although you should consider moving any such dependencies to the main process).

Example:

var browserify = require('browserify')
var renderify = require('electron-renderify')

var path = require('path')

var renderifyOpts = {
  windowRequire: ['leveldown']
}

browserify()
  .transform(renderify, renderifyOpts)
  .add('somefile-requiring-leveldown.js')
  .bundle()
  .pipe(process.stdout)

License

To the extent possible by law, we transfer any rights we have in this code to the public domain. Specifically, we do so using the CC0 1.0 Universal Public Domain Dedication.

You can do whatever you want with this code. No need to credit us, link to us, include any license, or anything else. But if you want to do those things, you're free to do that too.