Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runtime error for a build on window feat. electron-compile (forge) #1686

Closed
alexstrat opened this issue Jun 17, 2017 · 3 comments · May be fixed by qcif/data-curator#563
Closed

Runtime error for a build on window feat. electron-compile (forge) #1686

alexstrat opened this issue Jun 17, 2017 · 3 comments · May be fixed by qcif/data-curator#563
Labels

Comments

@alexstrat
Copy link

alexstrat commented Jun 17, 2017

  • Version: 19.4.2

Trying to build en electron-forge (electron-compile) project with builder on Windows. Build without error but the .exe fails to open with this error:

SyntaxError: unexpected token import

screenshot 2017-06-17 02 12 41

I prepared a reproduction repo here: https://github.com/getstation/forge-builder-example The screenshot is coming from this example.

# on windows
git clone https://github.com/getstation/forge-builder-example
npm install .
npm run pack
# open the .exe in /dist
@alexstrat
Copy link
Author

alexstrat commented Jun 19, 2017

Looking at the difference in the app.asar (after extraction) between Mac and Windows, it looks like the .cache on Windows is not populated correctly:
screenshot 2017-06-19 10 24 58

Whereas on mac (where I see no error):
screenshot 2017-06-19 10 28 15

@alexstrat
Copy link
Author

@develar have you had a chance to investigate this one?

If not, how can I help you? Do you have a hint where I should start looking?

@develar develar added the bug label Jun 21, 2017
@develar
Copy link
Member

develar commented Jun 21, 2017

19.6.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants