Upgrade to Quasar 2

[Beetix]

Following Quasar upgrade guide

[reinierl]

Do you have this running on your machine?

When I do npm run dev I run into this first:

 App · ⚠️  Quasar requires a minor change to the root component:
   /Users/reinier/Documents/cycleplanet/cycle-planet/src/App.vue

  Please add: id="q-app" (or write #q-app if using Pug)
  to the outermost HTML element of the template.

and then when I fix that:

 App •  ERROR  •  UI  in ./node_modules/@quasar/extras/eva-icons/eva-icons.css

Error: PostCSS plugin autoprefixer requires PostCSS 8.
  Migration guide for end-users:
  https://github.com/postcss/postcss/wiki/PostCSS-8-for-end-users

[Beetix]

In my case, I've used yarn run dev since Quasar recommends yarn over npm. But that shouldn't be the issue.

Can you try deleting .quasar, node_modules and package-lock.json (or yarn.lock). Then run npm (or yarn) install followed by npm (or yarn) run dev

[reinierl]

I wouldn't mind switching to yarn btw. I'll be hiking in the mountains for two weeks from this weekend on so I hope @bidsinga can take over reviewing this pull request.

[bidsinga]

I tried removing .quasar, node_modules and package-lock.json, and used yarn install and yarn run dev, but I keep running into errors. In my terminal I see messages for almost all pages saying:
App • WARNING • UI in ./src/pages/PageUser.vue
export 'staticRenderFns' (imported as 'staticRenderFns') was not found in './PageUser.vue?vue&type=template&id=09d36e9e&' (possible exports: render)

When the dev page opens, it keeps being white and a few errors, 2 of 3 from statcounter (CORS Policy), and 1 of 3 saying "Cannot read property 'version' of undefined"

Is it running stable on your device @Beetix?

[Beetix]

If you are using yarn you need to remove yarn.lock instead of package-lock.json.

Yes, I am also getting the same warnings. The page seems to open correctly on my side.