Hey @arusakov – looks pretty good, but I would like to explore making this its own repository before merging. I'll probably do that sometime this week.

If this only requires mangling filenames I'd like to figure out how we move this to server (ala getsentry/sentry#4090).

I'm wondering if we could just maintain the file:///(.+/)?[^/+].app/ pattern for stripping prefixes?

@getsentry/javascript

@dcramer
It's interesting. But one simple pattern in server code is not enough.
file:///(.+/)?[^/+].app/ pattern is good only for Electron apps for Mac OS X. For Windows app we need another pattern (maybe another for linux app). I need to research it.

@dcramer @benvinegar
Ok, I research it. Paths can be:
**/NAME.app/Contents/Resources/app/main.js - Mac OS X
**/NAME/resources/app/main.js - Windows and Linux

But you can bundle app to asar archive:
**/NAME.app/Contents/Resources/app.asar/main.js - Max OS X
**/NAME/resources/app.asar/main.js - Windows and Linux

Origin http://electron.atom.io/docs/tutorial/application-distribution/

@arusakov implemented the other path names in getsentry/sentry#4090

@arusakov – I appreciate the contribution, but our plan is to develop a plugin that leverages both raven-node and raven-js (so it can be used on both server and client). We'll refer back to this for posterity.

Can you suggest any temporary decision for electron?

@VladimirPal
You can see this in PR. Use electronPlugin._normalizeData as dataCallback for raven-js.

@arusakov Thank you, already did it.

// raven-electron-plugin.js
const PATH_MATCH_RE = /[^/]+$/;

function normalizeUrl(url) {
  const match = url.match(PATH_MATCH_RE);
  return match ? `~/${match[0]}` : url;
}

function electronPlugin(Raven) {
  Raven.setDataCallback((data) => {
    electronPlugin._normalizeData(data);
  });
}

electronPlugin._normalizeData = function normalizeData(data) {
  if (data.culprit) {
    data.culprit = normalizeUrl(data.culprit);

    const stacktrace = data.stacktrace || data.exception && data.exception.values[0].stacktrace; // eslint-disable-line
    if (stacktrace) {
      stacktrace.frames.forEach((frame) => {
        frame.filename = normalizeUrl(frame.filename);
      });
    }
  }
};

module.exports = electronPlugin;

// index.js - endpoint on my app
import Raven from 'raven-js';
Raven.addPlugin(require('./raven-electron-plugin'));

Note also that some users have reported (in #812) simply using raven-node in their electron apps. I haven't investigated what the difference in functionality might be, just pointing out the option/alternative.