Set a few environment variables to point the toolchains to your installation path. If your Visual Studio is installed in a directory other than the default, you'll need to.See the Chromium build documentation for more details on which Visual Studio.Visual Studio 2019 (>=16.0.0) to build, but Visual Studio 2022 (>=17.0.0) is preferred - download VS 2022 Community Edition for free.

For bundling and distributing your app code with the prebuilt Electron binaries, see the application distribution guide. It will open up an Electron window which will render your app along with Developer Tools opened side by side.Follow the guidelines below for building Electron itself on Windows, for the purposes of creating custom Electron binaries. This will add Electron mode automatically, if it is missing.

$ quasar dev -m electron '-' -no-sandbox -disable-setuid-sandbox $ quasar dev -m electron -no-sandbox -disable-setuid-sandbox # passing extra parameters and/or options to # underlying 'electron' executable:

If you want to jump right in and start developing, you can skip the previous step with “quasar mode” command and issue: $ quasar dev -m electron Please note that these are not problems with Quasar, but they are related to NPM and Windows. Set-ExecutionPolicy Bypass -Scope Process -Force iex ((New-Object ).DownloadString(‘’))Īnd then run choco upgrade python2 visualstudio2017-workload-vctools.Īt this point things should successfully install, but if not then you will need a clean installation of Visual Studio. In Powershell.exe (Run as Admin) npm install -global windows-build-tools seems to fail at the moment with errors pointing to python2 and vctools.

Electron create installer