Brand new Electron app does not start
-
I was in the middle of writing code for my Electron app, when it stopped starting. What I mean is that while before running
quasar dev -m electronresulted in my app being displayed, at some point that stopped actually happening.After some frustrating attempts to modify my code (and to undo some of the latest changes), I decided to try a brand new app, as created by quasar CLI. Below is the output in the Command Prompt (Win 10 x64). As you can see, I create a brand new app in the “test1” folder, added electron support, and then started the electron app. No changes to the generated code. And the result of all that is, well, nothing. No application shows up. The electron process shows up in the Task Manager, but there is no window displayed.
I am running quasar CLI @1.0.5, which is, I believe the latest. (I did an npm -g update before creating this new project.)
What can I do to address this issue?
C:\Users\Tibi\Projects\Quasar>quasar create test1 ___ / _ \ _ _ __ _ ___ __ _ _ __ | | | | | | |/ _` / __|/ _` | '__| | |_| | |_| | (_| \__ \ (_| | | \__\_\\__,_|\__,_|___/\__,_|_| ? Project name (internal usage for dev) test1 ? Project product name (must start with letter if building mobile apps) Quasar App ? Project description A Quasar Framework app ? Author Tiberiu Dumitrescu <tdumitr@hotmail.com> ? Pick your favorite CSS preprocessor: (can be changed later) Sass ? Pick a Quasar components & directives import strategy: (can be changed later) Auto import ? Check the features needed for your project: ESLint, Vuex, Axios, Vue-i18n, IE11 support ? Pick an ESLint preset: Airbnb ? Cordova/Capacitor id (disregard if not building mobile apps) org.cordova.quasar.app ? Should we run `npm install` for you after the project has been created? (recommended) NPM Quasar CLI · Generated "test1". [*] Installing project dependencies ... npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3. > node-sass@4.13.0 install C:\Users\Tibi\Projects\Quasar\test1\node_modules\node-sass > node scripts/install.js Cached binary found at C:\Users\Tibi\AppData\Roaming\npm-cache\node-sass\4.13.0\win32-x64-64_binding.node > core-js@2.6.11 postinstall C:\Users\Tibi\Projects\Quasar\test1\node_modules\core-js > node -e "try{require('./postinstall')}catch(e){}" Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: > https://opencollective.com/core-js > https://www.patreon.com/zloirock Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -) > core-js-pure@3.6.1 postinstall C:\Users\Tibi\Projects\Quasar\test1\node_modules\core-js-pure > node -e "try{require('./postinstall')}catch(e){}" > ejs@2.7.4 postinstall C:\Users\Tibi\Projects\Quasar\test1\node_modules\ejs > node ./postinstall.js Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/) > node-sass@4.13.0 postinstall C:\Users\Tibi\Projects\Quasar\test1\node_modules\node-sass > node scripts/build.js Binary found at C:\Users\Tibi\Projects\Quasar\test1\node_modules\node-sass\vendor\win32-x64-64\binding.node Testing binary Binary is fine npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN sass-loader@8.0.0 requires a peer of sass@^1.3.0 but none is installed. You must install peer dependencies yourself. npm WARN sass-loader@8.0.0 requires a peer of fibers@>= 3.1.0 but none is installed. You must install peer dependencies yourself. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules\webpack-dev-server\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules\watchpack\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) added 1468 packages from 617 contributors and audited 14368 packages in 75.424s 38 packages are looking for funding run `npm fund` for details found 0 vulnerabilities [*] Running eslint --fix to comply with chosen preset rules... > test1@0.0.1 lint C:\Users\Tibi\Projects\Quasar\test1 > eslint --ext .js,.vue src "--fix" [*] Quasar Project initialization finished! To get started: cd test1 quasar dev Documentation can be found at: https://quasar.dev Quasar is relying on donations to evolve. We'd be very grateful if you can read our manifest on "Why donations are important": https://quasar.dev/why-donate Donation campaign: https://donate.quasar.dev Any amount is very welcomed. If invoices are required, please first contact razvan@quasar.dev Please give us a star on Github if you appreciate our work: https://github.com/quasarframework/quasar Enjoy! - Quasar Team C:\Users\Tibi\Projects\Quasar>cd test1 C:\Users\Tibi\Projects\Quasar\test1>quasar mode add electron app:mode-electron Installing Electron dependencies... +0ms app:spawn [sync] Running "npm install --save-dev electron@^7.0.0 electron-debug@^3.0.0 electron-devtools-installer@^2.2.4 devtron@^1.4.0" +4ms > core-js@3.6.1 postinstall C:\Users\Tibi\Projects\Quasar\test1\node_modules\global-agent\node_modules\core-js > node -e "try{require('./postinstall')}catch(e){}" > electron@7.1.7 postinstall C:\Users\Tibi\Projects\Quasar\test1\node_modules\electron > node install.js npm WARN rollback Rolling back node-pre-gyp@0.14.0 failed (this is probably harmless): EPERM: operation not permitted, lstat 'C:\Users\Tibi\Projects\Quasar\test1\node_modules\watchpack\node_modules\fsevents\node_modules' npm WARN rollback Rolling back readable-stream@2.3.6 failed (this is probably harmless): EPERM: operation not permitted, rmdir 'C:\Users\Tibi\Projects\Quasar\test1\node_modules\watchpack\node_modules\fsevents\node_modules' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules\webpack-dev-server\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules\watchpack\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) + electron-devtools-installer@2.2.4 + electron-debug@3.0.1 + devtron@1.4.0 + electron@7.1.7 added 78 packages from 390 contributors and audited 14510 packages in 25.322s 40 packages are looking for funding run `npm fund` for details found 0 vulnerabilities app:mode-electron Creating Electron source folder... +28s app:mode-electron Electron support was added +30ms C:\Users\Tibi\Projects\Quasar\test1>quasar dev -m electron Dev mode.......... electron Pkg quasar........ v1.5.11 Pkg @quasar/app... v1.4.3 Debugging......... enabled app:quasar-conf Reading quasar.conf.js +0ms app:dev Checking listening address availability (0.0.0.0:8080)... +5ms app:webpack Extending Renderer process Webpack config +1s app:webpack Extending Main process Webpack config +555ms app:generator Generating Webpack entry point +10ms app:dev-server Booting up... +13ms Renderer process █████████████████████████ [100%] in ~9s Main process [0%] DONE Compiled successfully in 8653ms 10:26:24 PM i ｢wds｣: Project is running at http://0.0.0.0:8080/ i ｢wds｣: webpack output is served from i ｢wds｣: 404s will fallback to /index.html app:electron Building main Electron process... +9s Renderer process █████████████████████████ [100%] in ~9s Main process █████████████████████████ [100%] in ~2s app:electron Webpack built Electron main process +2s Hash: 5d1616f6f6dd4e4c1b05 Version: webpack 4.41.3 Time: 2033ms Built at: 12/30/2019 10:26:26 PM Asset Size Chunks Chunk Names electron-main.js 221 KiB electron-main [emitted] electron-main Entrypoint electron-main = electron-main.js WARNING in ./node_modules/electron-debug/index.js 96:45-58 Critical dependency: the request of a dependency is an expression @ ./src-electron/main-process/electron-main.dev.js @ multi ./src-electron/main-process/electron-main.dev.js WARNING in ./node_modules/electron-debug/index.js 97:61-74 Critical dependency: the request of a dependency is an expression @ ./src-electron/main-process/electron-main.dev.js @ multi ./src-electron/main-process/electron-main.dev.js app:electron Booting up Electron process... +5ms app:spawn Running "C:\Users\Tibi\Projects\Quasar\test1\node_modules\electron\dist\electron.exe --inspect=5858 C:\Users\Tibi\Projects\Quasar\test1\.quasar\electron\electron-main.js" +4ms Debugger listening on ws://127.0.0.1:5858/af08c58c-f9ef-41e3-ae69-66628d34495f For help, see: https://nodejs.org/en/docs/inspector -
Hello, Did you get an answer about this. I have the same problem with node-sass and 4.13.0 version