`electron-forge package` does not precompile anything

Please describe your issue: When running electron-forge package, it succeeds with the following messages, but the resulting package does still contain the uncompiled assets:

✔ Checking your system
✔ Preparing to Package Application for arch: x64
✔ Compiling Application
✔ Preparing native dependencies
✔ Packaging Application

Console output when you run electron-forge with the environment variable DEBUG=electron-forge:*. (Instructions on how to do so here. Please include the stack trace if one exists.

➜  vmxr git:(master) ✗ env DEBUG="electron-forge:*" electron-forge package
WARNING: DEBUG environment variable detected.  Progress indicators will be sent over electron-forge:lifecycle
  electron-forge:lifecycle Process Started: Checking your system +0ms
  electron-forge:lifecycle Process Succeeded: Checking your system +25ms
  electron-forge:runtime-config setting key: verbose to value: false +6ms
WARNING: DEBUG environment variable detected.  Progress indicators will be sent over electron-forge:lifecycle
  electron-forge:lifecycle Process Started: Preparing to Package Application for arch: x64 +0ms
  electron-forge:project-resolver searching for project in: /Users/sash/development/node/vmxr +3ms
  electron-forge:project-resolver electron-forge compatible package.json found in /Users/sash/development/node/vmxr/package.json +6ms
  electron-forge:packager packaging with options { asar: false,
  overwrite: true,
  afterCopy: [ [Function], [Function], [Function] ],
  afterExtract: [],
  dir: '/Users/sash/development/node/vmxr',
  arch: 'x64',
  platform: 'darwin',
  out: '/Users/sash/development/node/vmxr/out',
  electronVersion: '1.4.13',
  quiet: true } +7ms
  electron-forge:lifecycle Process Succeeded: Preparing to Package Application for arch: x64 +2m
  electron-forge:lifecycle Process Started: Compiling Application +3ms
  electron-forge:lifecycle Process Succeeded: Compiling Application +11s
  electron-forge:lifecycle Process Started: Preparing native dependencies +1ms
  electron-forge:lifecycle Process Succeeded: Preparing native dependencies +103ms
  electron-forge:lifecycle Process Started: Packaging Application +0ms
  electron-forge:lifecycle Process Succeeded: Packaging Application +26s

What command line arguments are you passing?

None

What does your config.forge data in package.json look like?

{
  "make_targets": {
    "win32": [
      "squirrel"
    ],
    "darwin": [
      "zip"
    ],
    "linux": [
      "deb",
      "rpm"
    ]
  },
  "electronPackagerConfig": {},
  "electronWinstallerConfig": {
    "name": ""
  },
  "electronInstallerDebian": {},
  "electronInstallerRedhat": {},
  "github_repository": {
    "owner": ""
  },
  "windowsStoreConfig": {
    "packageName": ""
  }
}

Please provide either a failing minimal testcase (with a link to the code) or detailed steps to reproduce your problem. Using electron-forge init is a good starting point, if that is not the source of your problem.

AFAIK there’s nothing special about my app, so it should happen with every electron-forge initiated app

[MarshallOfSound]

@saschagehlich For your own personal research I’d recommend comparing your app .compilerc do the .compilerc output by a simple electron-forge init.

[MarshallOfSound]

@saschagehlich You should look into your compilerc config you have. transform-runtime relies on babel-runtime. It’s intention is to reduce the overall package / bundle size by extracting babel logic from each file into require calls. It’s quite complicated so you should look into it yourself.

Closing this out as a user config issue 👍