Thanks! I understand that one will have to change the dependency in the package.json to v5 manually in order to update from v4?

Now, to figure out why the marker png’s don’t work with Webpack.
net::ERR_INVALID_URL

in quasar.conf add the css to the css arrray:

css: [
      '~leaflet/dist/leaflet.css',
      ...otherCss
    ],

Just a note: Be sure the style is not scoped to your component.
In Electron this works:

<style>
input[type="number"]::-webkit-outer-spin-button,
  input[type="number"]::-webkit-inner-spin-button {
    -webkit-appearance: none;
    margin: 0;
  }
</style>

But, <style scoped>…</style> doesn’t.

Scoping the style appears to work in browsers, but failed for me in Electron.

Testing out the new modern flag for an Electron app build (Electron v9.0.0) and getting a build error.
Unexpected token
The error appears at areas of code using Nullish coalescing operator ??
Removing the -modern flag and running Quasar dev -m electron then builds successfully.
Is there something about the Nullish coalescing operator that is not modern or why does it throw an error?

@rstoenescu understood. Thank you!

Thanks! I understand that one will have to change the dependency in the package.json to v5 manually in order to update from v4?

@nothingismagick should I just install vue-croppa as a dependency in my Quasar v1 project? What is the best way to import non Quasar vue-components?

@mstarr I hear ya! Cheers!

@mstarr not sure if you have seen this project: https://github.com/quasarframework/app-extension-typescript
In fact, Vue itself is moving in that direction: https://vuejs.org/v2/guide/typescript.html

I expect better TS support will be baked into Vue and, therefore, by extension Quasar.

I too have been trying to get QSelect to work without having to write a new filter for each select. Very tedious and error prone. I have been posting my woes over on the Discord channel too, regarding adding a new value and acceptinging it with tab key instead of return then tab. I tried to see if we could even get a new QAutocomple or other such functionality. Hopefully there will be a better solution than the current QSelect option. At this point, I feel I’m going to have to create my own Vue component for this. I have a person add/edit dialog that is already over 600 lines if code. Mostly for redundant filterFN for each QSelect. It appears that QSelect is really only intended for simple arrays of strings. It gets really cranky if it receives as options data it doesn’t expect. Which really complicates code. However, that said, I may be expecting too much from the tool and should be using something else or destructuring my source data using …map() perhaps but there, again, not dynamic. Sorry this sounds like a rambling rant, it really isn’t. I love Quasar. I need better a Vue and JS skillset.