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

Error with Electron-Webpack 4.28.4 #94

Open
dbhagen opened this issue Mar 8, 2019 · 2 comments
Open

Error with Electron-Webpack 4.28.4 #94

dbhagen opened this issue Mar 8, 2019 · 2 comments

Comments

@dbhagen
Copy link

dbhagen commented Mar 8, 2019

  • The target platform(s) the problem occurs on (Linux, Mac, Mac App Store, and or Windows): Mac
  • Node version (run node -v): ➜ node -v v11.10.1
  • auto-launch version: "auto-launch": "^5.0.5",
  • The options you're passing to auto-launch: See code snipet below.
  • Are you using NW.js or Electron? Electron
    • If so, which version? "electron": "4.0.1", "electron-builder": "20.38.4", "electron-webpack": "^2.6.2", "webpack": "4.28.4"
    • If you're using Electron, are you using auto-launch from the main process or a renderer process? Main process
  • Can you reproduce this with a simple Hello World example app? Using clone of electron-webpack-quick-start.
  • If needs be, would you be able to provide us with a simple app (as simple as possible) which reproduces the problem? See code snipet below

Clone project:
//create a directory of your choice, and copy template using curl mkdir new-electron-webpack-project && cd new-electron-webpack-project curl -fsSL https://github.com/electron-userland/electron-webpack-quick-start/archive/master.tar.gz | tar -xz --strip-components 1 //install dependencies yarn

Install module:
yarn add auto-launch

Add the following code to ./src/main/index.js:
import { autoLaunch } from 'auto-launch' // Global Auto Launch references var appAutoLaunch = new autoLaunch({ name: 'Hello World App', isHidden: true })

@dbhagen
Copy link
Author

dbhagen commented Mar 8, 2019

Just, just a curious note and workaround...
Swapping import { AutoLaunch } from 'auto-launch' with var AutoLaunch = require('auto-launch') fixes it. Up to you if you want to keep this issue open. At least I can work around it.

@adam-lynch
Copy link
Contributor

Please see that we're looking for contributors / maintainers: #64.

I'm happy to give access to people who are willing to help improve things, merge pull-requests, close issues, etc.

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

No branches or pull requests

2 participants