sentry-electron: TypeError: mod.require is not a function

I just released 0.15.0; could you guys try the following, if you have this issue instead of importing and using init like:

import * as Sentry from '@sentry/electron'
Sentry.init({...});

Use init on the main process with a deep import like:

import { init } from '@sentry/electron/dist/main'
import * as Sentry from '@sentry/electron'
init({...});

If this works I will write this into the docs.

We are now bundling both main and renderer processes with webpack. We use:

const { init } = (process.type === 'browser'
  ? require('@sentry/electron/dist/main')
  : require('@sentry/electron/dist/renderer'))

And then use the Webpack DefinePlugin:

    // main process
    plugins: [
      new webpack.DefinePlugin({
        'process.type': '"browser"'
      }),

   // renderer process
   new webpack.DefinePlugin({
     'process.type': '"renderer"'
   }),

This means that when bundling each process, Webpack replaces process.type with a constant and then removes the inaccessible code:

const { init } = ('browser' === 'browser'
  ? require('@sentry/electron/dist/main')
  : require('@sentry/electron/dist/renderer'))

// becomes >

const { init } = (true
  ? require('@sentry/electron/dist/main')
  : undefined)

@HazAT Could this be fixed? It’s been one year now and nearly any Electron trying out Sentry will waste hours on this and be left without any satisfactory solution. This is not up to par with Sentry overall quality.

Can you try to do this: https://github.com/getsentry/sentry-electron/issues/92#issuecomment-452649698

To make this work in both main and renderer, I ended up monkey-patching the dispatch function:

require('@sentry/electron/dist/dispatch').specificInit =
    process.type === 'browser'
        ? require('@sentry/electron/dist/main').init
        : require('@sentry/electron/dist/renderer').init;

This is because we’re webpacking node_modules into our electron app (rather than shipping as node_modules) and we actually really want the normal require rather than the dynamic one electron is trying to use.

What if this project used a normal require, and for webpack builds you can always specify @sentry/electron as an external if you don’t want it to bundle it.

Getting the same error here, using Electron 3 We are using the Vue-CLI boilerplate, so you should be able to reproduce the error easily using https://github.com/nklayman/vue-cli-plugin-electron-builder

Not really sure were to start digging thought, first time using Sentry

@rlugge if it was possible to merge this into Sentry, I would have already submitted a PR 😁.

sentry-electron has to cater for many different development scenarios and it prioritises the most common which is bundled renderer and non-bundled main. For this most common scenario, there should be no special bundler configuration required and the renderer should not end up with all the unused Sentry main process code. dynamicRequire currently helps fulfil this and if it doesn’t for any reason, you should open a new issue about this.

Once the main process is bundled with Webpack, the node module object is often not available so the dynamicRequire call fails. Even if module.require() was available it’s likely the './main' code was never bundled.

Likely the simplest solution is to also expose InitMain() and InitRenderer() and leave it up to the developer to ensure the correct one is bundled and called, whether that be with help from webpack.DefinePlugin or some other means.