devtools-next icon indicating copy to clipboard operation
devtools-next copied to clipboard

Vue 3.1.0 project detected as Vue 2

Open Derranion opened this issue 1 year ago • 9 comments

On my current project Vue ^3.1.0 is used.

After the recent Vue Dev Tools update it started to detect it as Vue 2 project.

This forced Dev Tools to use some outdated version.

Update: 3.4.35 is the Vue version, Vue Dev Tools version in the plugin section is 7.6.3 but it looks significantly different to what we had 1 week ago.

DevToolPluginVersionDroppedDownSignificantly

Current workaround I found is to use legacy v6 plugin: https://chromewebstore.google.com/detail/vuejs-devtools/iaajmlceplecbljialhhkmedjlpdblhp?utm_source=ext_sidebar?utm_source=ext_sidebar

But would be great to resolve this, not sure why this is happening.

Could be related to options API syntax used in the app but this is still a valid Vue 3 syntax.

Thanks in advance.

Derranion avatar Nov 04 '24 20:11 Derranion

This is a bit strange, do you have multiple instances of vue in your app? This is not related to the options API, which is supported in v7. If we can provide minimum repo, it will help us locate the issue.

webfansplz avatar Nov 05 '24 03:11 webfansplz

The v3.4.35 in the orange block is not the devtools version, but the installed Vue version 🤔 Your screenshot clearly shows the UI of v7. You probably specify ^3.1.0 in your package.json, so the installed Vue version is 3.4.5 since it respect the semver limitation.

mrleblanc101 avatar Nov 05 '24 15:11 mrleblanc101

v3.4.35 is your project vue version instead of the current vue-devtools version, if everything works fine that might be a vue version detection bug.

alexzhang1030 avatar Nov 06 '24 14:11 alexzhang1030

Or that they don't know the difference between the minimum requested version in the package.json and the installed version in the lockfile.

mrleblanc101 avatar Nov 06 '24 14:11 mrleblanc101

Or that they don't know the difference between the minimum requested version in the package.json and the installed version in the lockfile.

You can try devtools functions if they can work properly, looks like problems have been resolved, right?

alexzhang1030 avatar Nov 06 '24 14:11 alexzhang1030

@alexzhang1030 I'm not OP, I think OP is confused, I don't think there is a bug

mrleblanc101 avatar Nov 06 '24 14:11 mrleblanc101

@alexzhang1030 I'm not OP, I think OP is confused, I don't think there is a bug

Oh, sorry... But anyway thanks

alexzhang1030 avatar Nov 06 '24 14:11 alexzhang1030

The v3.4.35 in the orange block is not the devtools version, but the installed Vue version 🤔 Your screenshot clearly shows the UI of v7. You probably specify ^3.1.0 in your package.json, so the installed Vue version is 3.4.5 since it respect the semver limitation.

This is correct, package.json version used in the project is "vue": "^3.1.0".

For some reason I thought that Vue Dev Tools version can be found in the plugin info but it is a Vue version instead indeed.

In any case I don't know which exact Vue Dev Tools version is used, plugin itself shows Version 7.6.3: image

It looks this way: devToolsUnknownVersion

One week ago it looked significantly different.

Not sure if this is expected.

If this is just a new design - ticket could be closed, because I didn't see these changes in the recent releases: https://github.com/vuejs/devtools/releases

Derranion avatar Nov 06 '24 17:11 Derranion

The extension was updated from v6 to v7. I believe the initial version of v7 is 7.6.0. 7.0.0 to 7.6.0 were in Vue Devtools Next for testing I think.

mrleblanc101 avatar Nov 06 '24 18:11 mrleblanc101