I have an electron app and want to open a new Browserwindow with a specif quasar - module (route) within. I know that this will be a second vue app for its own and this is fine because i need a new process there.

I found this solution:

[https://forum.quasar-framework.org/topic/6548/how-to-open-a-specific-route-in-an-electron-browserwindow](link url)

but i don’t get it how it works (I do not understand how to bring openUrl and “to” attribute together to open a window with specifc route).

@dobbel

thanks, but did not help:
even commenting out complete block has no effect. What helped was to add /src to .eslintignore. Now all is ignored which is fine to get it run but not for real developing…

extendWebpack (cfg) {
        // linting is slow in TS projects, we execute it only for production builds
        if (ctx.prod) {
          cfg.module.rules.push({
            enforce: 'pre',
            test: /\.(js|vue)$/,
            loader: 'eslint-loader',
            exclude: /node_modules/,
            options:{
              emitWarning : true,
              emitError : false
            }
          })
        }
      }

I am just toying with quasar electron. but i do not get it to build the app, because i allways get linting errors which stop the build.

did just (latestest versions) without any changes to the default demo app that comes with quasar out of the box:

quasar create test-app # (selected typescript support and standard linting)
quasar mode add electron 
quasar dev -m electron # linting errors but works 
quasar build -m electron # liniting errors  stop build

after first run i got 10 liniting errors. after i tried to fix or ignore them i got new errors, this seems not to end. and now i am at a point i don’t know how to fix or ignore current linting errors.

Linting may be a fine thing, but can i allow electron app to be build despite of linting errors?