Ideas & Suggestions #111
Replies: 14 comments 7 replies
-
@webfansplz Great little tool! My one nice to have would be to have the devtools bar aligned either top, left, right or bottom. As currently it cuts over some important UI/UX. Other than that, really cool! |
Beta Was this translation helpful? Give feedback.
-
The lines in the background and the lines on the page are a bit confusing |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I would love to see the Tanstack Query/Vue Query tab integrated inside the new Vue DevTools. I think in the "old/current" DevTools it was automatically detected and supported. |
Beta Was this translation helpful? Give feedback.
-
Is there a way to avoid it activating a button/link when trying to access the component data of that element? |
Beta Was this translation helpful? Give feedback.
-
Is there a way to see Component Events? |
Beta Was this translation helpful? Give feedback.
-
I suggest you for this beautiful DevTools Tool to add plugin and modules section like a Nuxt.JS DevTools. See idea from this image. |
Beta Was this translation helpful? Give feedback.
-
Maybe make the Dark/Light setting ("Settings/Appearance") not "dark" by default. It took quite some time to understand where the "dark" class in my root element comes from. My suggestion: "None (or OS?), Light, Dark" with "None" as default |
Beta Was this translation helpful? Give feedback.
-
it would be nice to have a filter on Component Tab to filter props, computed, etc by a string |
Beta Was this translation helpful? Give feedback.
-
A way to (always or easily) open it in a new window. Our scenario has us use the tool in a very constrained space (addin to an application). What works is using And the normal floating panel isn't very useful when using the separate devtool window, maybe automatically hiding it could be good. Though not really necessary, the setting works tool. Stand alone with |
Beta Was this translation helpful? Give feedback.
-
Sometimes I would like to interact with a component in the developer console, calling methods and updating properties. It would be great if clicking on a component in the "Components" tab would store a reference to the component instance in a global variable like (I guess it would be great to allow console commands directly within the Vue Devtools pane itself, especially useful on mobile devices without a console, but I can also see that getting quite complex if you wanted autocomplete etc., so the request above is a lot simpler to implement.) |
Beta Was this translation helpful? Give feedback.
-
A small Although the syntax of Vue3 hasn’t undergone significant changes, there are still some functional improvements (such as new features) between minor versions. We can write a simple codemod tool to help users easily migrate their syntax. For example, Vue3.4 introduced a new feature At the same time, this tool will also evolve with the iterations of Vue, presenting the new features of the latest Vue version to users in a more intuitive way. |
Beta Was this translation helpful? Give feedback.
-
Would be really nice if there was a way to enable it to run in 'prod'/'build' mode. This may be very challenging or a non-starter because of the dependency on vite dev server, but with the old/current vue devtools browser plugin you can make it run on prod with some console commands and this can be extremely valuable |
Beta Was this translation helpful? Give feedback.
-
Is it possible to display the relative path of the file when hovering on open in editor? |
Beta Was this translation helpful? Give feedback.
-
Any ideas & suggestions always welcome 👇
Beta Was this translation helpful? Give feedback.
All reactions