[Qv2] new project issues

[ssuess]

After creating a new project (quasar create testv3 --branch next, configed to use Vuex, Vue-i18n, TypeScript, Axios, & ESLint) I notice a couple of things:

• should the beta version of Vue (chrome) devtools be working? I get a blank panel (although the panel is there)
• notice that eslint complains about double quotes and semi-colon in /store/store-flag.d.ts

[dobbel]

@ssuess said in [Qv2] new project issues:

quasar create testv3 --branch next

I am trying to mimic what you have done when creating a new quasar project. What did you choose for component style?

1. Composition APi
2. Class-based
3. Options Api

ESLINT style?
-Prettier
-airbnb
-standard

I choose prettier and I have no eslint complains.

Yarn or NPN?

Btw the one Component created with the Composition Api reads like a big mess to me with a ton of boilerplate code( all those silly imports from Vue) that was not necessary before with the Options Api.

[s.molinari]

I chose standard and had issues with semi-colons. I did a yarn lint --fix and all was ok after that.

I also have no trouble with Vue Dev Tools. Just make sure you have the beta version for Vue 3.

Scott

[ssuess]

@dobbel sorry I should have specified. I am using Composition API, and standard ESlint style

[ssuess]

@s-molinari I am using the latest beta of devtools as well, like you. But for some reason, although the vue panel shows in the dev tools and has a header, everything below is blank:

[s.molinari]

@ssuess - This is what I see. Did you by chance turn off the other Vue Dev Tools extension?

Scott

[ssuess]

@s-molinari I did turn the other one off (but I did not uninstall it, if that matters)

[s.molinari]

@ssuess - Naw. I have the older one installed still too. I doubt it has anything to do with it (just looking for possible differences), but I have localhost as the URL. You have 127… the IP address. Interesting too is the “3” is lit on the Vue logo in my setup. Hmm…

Scott

[ssuess]

@s-molinari I probably just typed 127.0.0.1 in by mistake and it reloaded it. Here is the dev env restarted (with command quasar dev nothing else), loading up localhost. btw, the “3” is just news, once clicked on it will go away I had it too.

[ssuess]

I should add I did make some very slight mods to the embedded component (added another property to the list items), so maybe that had some effect. I will revert and see if it make a difference.

[ssuess]

nope. same problems.

[s.molinari]

I have no idea what’s wrong. Vue Dev Tools works as it should for me. (Just learned about the notifications though… )

Scott

[dobbel]

@ssuess

Could also be a difference between MacOS Chrome vs Windows OS Chrome behavior.

[s.molinari]

Oha. Yep. Have you tried Firefox with the devtools extension?

Scott

[ssuess]

yay it works in FF on Mac, perhaps the platform was the problem:

[s.molinari]

It’s still beta. I’d report your issue to the Vue Dev Tools repo. @ssuess

Scott