Whatever QPopupProxy has for it’s default slot, this is where you would adjust height and width, commonly via style="width: 300px; height: 400px;"

@matroskin Glad to have helped and hope we have another yarn convert. Unfortunately, with issues at npmjs, the tool has been going down hill.
I would be interested in knowing, if you create the project could then be converted to use npm?

https://github.com/quasarframework/eslint-plugin-quasar/releases/tag/v1.0.0-alpha.16

• fix(QProxyPopup): context-menu is valid property

This is how QPopupProxy works (with QMenu and QDialog)

@erakis
The fact of the matter is that this is a localized issue. No one is having the same issue. I regularly debug js and vue files without issues. So, why is it happening to you? No ideas.
Hit me up on discord and I can show you images that look like what you should have.

https://github.com/quasarframework/quasar-ui-qcalendar/releases/tag/%40quasar%2Fquasar-ui-qcalendar-v1.0.1

• fix(ui): QCalendar no longer needs a width to display properly

@erakis
This has nothing to do with Quasar. This is how webpack works. And, they have been busy making things better. I don’t know why your situation is different. Would be nice if you were able to try this on a new system (like Virtualbox ubuntu/windows). Just to make sure it’s not your own issue. I still feel it’s one of your installed globals that needs updating. Or, you migrated from 0.17, but kept some of the 0.17 configuration, instead of using the v1.

https://github.com/quasarframework/quasar-ui-qiconpicker/releases/tag/%40quasar%2Fquasar-ui-qiconpicker-v1.0.4

• fix(ui): prevent divide-by-zero scenario

https://github.com/quasarframework/eslint-plugin-quasar/releases/tag/v1.0.0-alpha.15

• feat(rule): ‘quasar/no-invalid-qfield-usage’

Add this rule in your eslintrc.js in the rules section:
‘quasar/no-invalid-qfield-usage’: ‘warn’

I think this really depends on how you did your migration.
Did you create a new project and migrate your source code only?
If so, then I don’t think that would be the problem.
If not, then you probably missed something for configuration.