Nice, thanks for opening that issue.

I was looking around a bit for a file, maybe in a hidden directory, that is created when I see quasar dev show: “app:quasar-conf Generating Webpack config +6ms”, but I did not find one.

I’m using webstorm and I am able to just ignore it not finding quasar ( and now its not really imported much I suppose ), but I am adding a couple alias to quasar.conf.js and I am looking for what I can point Preferences->Languages & Frameworks->JavaScript->Webpack at so it picks the alias up since I will actually be importing those.

Cool, thanks! Will take a look at this

Thanks, book marking for a later time.

Awesome! Can we start looking at what needs to be done to upgrade now, or should we wait?

Oh, ha! Ok.

I might be blind where is the option to mark something as solved?

I have been able to fix that error one by not changing the route until after the close callback is called on a modal I was seeing it from. For example:

layout.hideLeft(() => {
// now change the route.
})

Thank you!

Here is what I had to do:

Install the Inappbrowser plugin:
http://cordova.apache.org/docs/en/latest/reference/cordova-plugin-inappbrowser/index.html

Use:
window.cordova.InAppBrowser.open(url, ‘_system’)