Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

ES6 is not supported after Electron packaging

I'm using various ES6 syntax (such as import etc.) & React code (JSX) in my Electron-based application. During the development, I'm using the electron-prebuilt-compile package (as a dev-dependency) in order to support these new features and it works perfectly fine without any errors.

But after packaging my app using the electron-packager package and running the distributable application file, I experiencing unsupported ES6-related errors such as:

Unexpected token import

That's is how I run the electron-packager command (notice to the platform & architecture flags):

electron-packager . MyCoolApp --platform=linux --arch=x64

Any reason why a packaged/distributable version of my application does not support ES6/React features?

like image 641
Yair Nevet Avatar asked Mar 29 '18 12:03

Yair Nevet


1 Answers

Solved.

it turns out that devDependencies are being omitted during packaging by default, which means that the electron-prebuild-compile package is "out of the game" for a packaged application and without it ES6 can't be transcompiled. So in order to deactivate this default behavior, I had to call the packager command with the --no-prune flag so that the devDependencies will remain without being deleted:

electron-packager . MyCoolApp --platform=linux --arch=x64 --no-prune

In addition, I had to introduce a new script (let's name it: es6-init.js) for initialization of the main app's script in order to "compile" the code before rendering (it should be used as the main entry point script of your application):

var appRoot = path.join(__dirname, '..');

require('electron-compile').init(appRoot, require.resolve('./main'));

References:

  • https://github.com/electron-userland/electron-compile#how-does-it-work-slightly-harder-way
  • https://github.com/electron-userland/electron-packager
like image 134
Yair Nevet Avatar answered Sep 25 '22 21:09

Yair Nevet