Check if code is running in Electron renderer process
Latest commit 20aa3f6 Sep 25, 2016 @jprichardson 2.0.1
Failed to load latest commit information.
.gitignore initial commit Jul 4, 2015 2.0.1 Sep 25, 2016
index.js Remove trailing spaces Sep 25, 2016
package.json 2.0.1 Sep 25, 2016 readme: update Jul 14, 2015
test.js initial commit Jul 4, 2015


Check if code is running in Electron renderer process.


Electron code can run in either the main process or the renderer process. This is the same as asking if the code is running in a web page with access to the DOM or not. Read more here:

Use Cases:

  • Creating a single module that acts differently whether it's running in main or renderer.
  • Logging utility. One process (main) would be responsible for writing to log files, while renderers would send log data to the main. Would allow your code to have one log method.
  • Testing. Your test code may behave differently if the DOM is available.
  • Normalize console.log behavior. console.log behavior is weird in renderer, this can easily be fixed.

Why Use a One Line Module?

Excellent discussion here: If that doesn't convince you, then maybe the fact that Electron could change the way that they inherit global in renderer and if they do, you would have to change your code whereas if you used this module, you'd just have to update to the latest version =)


npm i --save is-electron-renderer


You'll notice that when using console.log in Electron that in the renderer process outputs some weird log level garbage to stderr before your actual console message. You can normalize this behavior:


// clean up Electron output
function hook () {
  var isRenderer = require('is-electron-renderer')
  var pre = '(' + (isRenderer ? 'RENDERER' : 'MAIN') + ') '
  console.log = function (msg) {
    process.stdout.write(pre + msg + '\n')

module.exports = {
  hook: hook



output (main):

(MAIN) hello

output (renderer):

(RENDERER) hello


var isRenderer = require('is-electron-renderer')
// => (BOOLEAN)



Copyright 2015 JP Richardson