electron-compile | Electron supporting package to compile JS | Dektop Application library

Preload script is different kind, you can't directly point typescript in there. Only possible way is make javascript preload script which bootstraps electron compile inside of it (since you are using electron-prebuilt-compile), and require typescript files inside of it. It is somewhat verbose and require additional overhead into, I honestly not strongly recommend for it.

I had a similar issue and it ended up being related to yarn version. I fixed it by installing yarn this way:

I think i found the solution myself.

The problem is with the "electron-compile" module. After running "electron-forge package" it seem to interfere when loading my custom binary files and prevent them from being loaded correctly via XMLHttpRequest.

The solution seems to use the "addBypassChecker" that comes with the electron-compile package to ignore files to be recompiled by electron-compiled if they are not part of the App.

I checked the distributable file and found the whole source code inside it, so I guess it's because it has to compile typescript every time?

This is not true. Current stable uses electron-prebuilt-compile (https://github.com/electron-userland/electron-forge/blob/1709af0bc53bd962466dd2025672b95f2e9399cc/packages/api/core/src/util/electron-version.ts#L6) which creates precompiled cache for typescript files for packaging time. Typescript source is only needed for module resolution in actual filesystem.

there will be a blank screen for a while before the app actually load especially the first time

This requires profiling application itself to find out what is happening in meanwhile. It is possible module resolution takes long or either any js execution time's blocking, but can't tell without profiling it.

You may not use webpack for project created via electron-forge. It is not impossible thing, but you'll need various custom configuration to make it work.

electron-forge is constructed based on electron-compile, which registers on-the-fly transpilation hook in electron process. When you build package via electron forge's preset build script it'll generate correct dependency set along with your module dependency. electron-compile is one, it is mandatory required dependency but your webpack config breaks those.

TL:DR;

1. electron-forge has own flows
2. run webpack then pkg via forge can break thing.

I'd recommend take one way only (between webpack vs. forge), customization to mix it would not be trivial for first time setup.

This is electron issue. There is a bug opened for this and it will be fixed in one of the future releases.

'ES7' is ambiguous and technically incorrect term, because it colloqually referred to proposals that weren't included into ES6 (currently as ES.next), but also had referred to ES2016.

Package description refers to ES2016. While decorators are not a part of existing standards and supported in Babel via a plugin.

The package explains that it respects user .babelrc file, so it should contain transform-decorators or transform-decorators-legacy in presets section, and respective Babel plugin should be installed.

Hey so I just had a similar issue as you. I am using Socket.io in my project and when trying to run electron-forge package I was encountering the same errors as you. In order to get it working I removed the dependency "socket.io": "^2.0.3" from my package.json and I was then able to package it without issue. Hope it helps!

As soon as @MarshallOfSound released the new version it works fine