AI product readChrome DevTools extension for debugging and inspecting Vue.js applications
Provides developers with specialized tools to inspect, debug, and profile Vue.js applications directly in Chrome DevTools, which is not possible with standard browser DevTools alone
1. Install extension and navigate to a page with Vue.js. 2. Extension automatically detects Vue.js via content scripts (prepare.js runs at document_start in MAIN world). 3. Extension popup shows Vue detection status (enabled/disabled/Nuxt/VitePress). 4. Open Chrome DevTools and find the Vue panel. 5. Inspect component tree, view component state/props/events, debug application state. 6. Use graph visualization to understand component relationships.
Detects Vue.js presence on web pages and shows detection status in extension popupAdds dedicated Vue panel to Chrome DevTools for component inspectionDisplays component tree hierarchy with parent-child relationshipsInspects component state, props, computed properties, and emitted eventsSupports Vue 2 (with migration guide to Vue 3) and Vue 3 applicationsDetects and provides specialized icons for Nuxt and VitePress frameworks
- Target users
- Vue.js developers / Frontend developers building with Vue.js framework / Developers using Nuxt.js or VitePress / Frontend developers debugging Vue component hierarchies and state
- The extension source code is minified, making some analysis less precise. However, the core architecture is clear from entry files and manifest.
- Cannot verify if external Vue.js ecosystem tools (like Vue DevTools desktop app or VS Code extension) have paid features, but this Chrome extension itself is completely free.
- The large vis.js graph visualization library (1.9MB) contains many false positive keyword matches that are part of the library code, not the extension's own functionality.
MonetizationNo paid features detected
Vue.js devtools is a completely free, open-source developer tool (GitHub: vuejs/devtools). There are no payment mechanisms, subscription models, feature gating, or upgrade prompts anywhere in the codebase. The 'pro' keyword matches are all false positives hitting Vue component 'props' properties and Object.prototype methods. The extension has no integration with payment platforms, no billing APIs, and no premium feature indicators.
- Confidence
- 95
- Payment platform
- --
- Source
- AI / High
- Login required
- No
- Reason
- Vue.js devtools is a local browser extension that works entirely within Chrome DevTools without requiring any user authentication or account creation. The extension operates by injecting scripts into pages to detect Vue.js instances and communicate with a devtools panel. No login UI, authentication flows, or account management features exist in the codebase. The keyword matches for 'token', 'session', 'account', and 'auth' are all false positives from the vis.js graph visualization library (HammerJS touch sessions), DOM token lists, MIT license text, and mathematical comments like 'accounting for the positions'.
I used to love this extension. With the latest update it has become almost completely useless for Vue 2 projects. Is there a way to go back to a previous version of this plugin?
After v6, it is unsable
Used to be the best extension out there but no longer updates reactively since it was "auto updated" to the vue3 version making it essentially useless
支持了vue3,666
Crashes all the time. Cannot use it for about a year now.
Tự nhiên bị update phiên bản mới, không quen tí nào :(
다 좋은데요..components 옆에 events등등 다른 버튼들 어딧죠?
更新之后很多组件识别不出
I just use vue.js devtool beta and this is the update I've been waiting for :)
It was working ok (albeit with some frequent crashing), but this latest update has rendered it unusable. It just completely breaks my website when I open up the dev tools and shows errors in the console like "uncaught (in promise) TypeError: sub is not a function". Please revert back to previous version. This version is not fit for purpose. It crashes in a function "Store.prototype.dispatch = function dispatch 9_type, _payload)" on the "this._actionSubscribers.forEach" line.