@quasar/app v2.0.0 released! Major improvements

[amoss]

I started from the beginning and now it seems to work

[zodd]

Congratulations on the release and the hard work! Thanks for this great framework.
Updating as soon as a few extensions like qenv have caught up

[codenamezjames]

Congratulations! excited to try it out.

Heads up, Qcalendar has an issue with 2.0 but I talked with @Hawkeye64 and he said he is working to get a new version of Qcalendar out the door right now so it probably won’t be an issue by the time your reading this.

[Cris-Malinescu]

Hello folks, FYI my feedback with regard to upgrading quasar/app to v2 and following the steps as described here https://quasar.dev/quasar-cli/app-upgrade-guide.
It went smooth and perfect, congratulations for the great work - rarely one encounters these days a framework major version migration without problems just following
the provided steps - this is effective and efficient time saving, thanks!

[Cris-Malinescu]

@zodd I’m using dotenv - smooth, no issues;

[dannyalder88]

Running quasar upgrade did not work for me so had to yarn install 2.0.0 but everything else went smoothly. I’ve noticed one issue though, importStrategy: 'auto' does not seem to import any Quasar components referenced inside a functional Vue component which means I now have to import all components as I can no longer specify a list of the ones I am using. Is this a limitation of how auto works or is it something that could be fixed?

Great work overall though guys!

[darkkeyper]

This post is deleted!

[metalsadman]

@dannyalder88 import the component/directives locally.

[amoss]

I want to join to the greetings and thanks regarding the hard work, this is not taken for granted. I do want to share my experience with the upgrade. The upgrade itself, went smooth except for

1. quasar upgrade didn’t upgrade quasar/app, only quasar itself. I needed to manually update quasar/app. @dannyalder88 mentioned that as well.
2. Once I deleted node_modules folder and ran npm_install, everything stopped working. quasar dev ran ok, the console tab is empty but in the network tab I see several 101 and 304 status codes (instead of 200) and neither the main layout (app.vue) nor the first page (login) were shown.

Has anyone encounter this? If you’re going to delete node_modules, don’t forget to backup your folder.

[amoss]

I can’t edit my post so here’s the image of what I see

[kikan]

Followed the upgrade guide (https://quasar.dev/quasar-cli/app-upgrade-guide), well written, clearly explained and easy to follow.
Everything is OK, thank you for your great work.

[s.molinari]

For everyone who finds the rare issue or two, please start a new thread. It is easier to help you that way. Thanks!

Scott