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'.
是真的卡,如果你用的是Vue2,目前只能用这个, Vue3 + vite 用这个工具吧 https://devtools-next.vuejs.org
这个版本卡死了, 刷新了就不显示了! 艹
控制台打开就几百条报错, 这么久了怎么还没修啊...
The latest version stops working all the time, requiring you to close and re-open the devtools and navigate back to where you were working. Seems like HMR may be breaking it. It's also breaking vee-validate's plugin.
почему он перестает работать после изменение файла в дев режиме?
Kind of broken, You need to keep closing and opening the devtools to get it to refresh. But it is usable, its just annoying to have to keep it updated.
As like others have mentioned, it works 100%, 20% of the time. Basically doesn't. And even if it works, it's stuck in a loading screen and won't work after reloading. Don't count on this. This is probably why people use React instead me thinks
非常非常卡 新排版很好看 也很方便。但是太卡了 。。刷新几次就需要重新打开开发者工具 好像和页面断开了链接 选中功能不好使 。devtools主页面也会卡死
The developer experience is so awful. It works for a bit until it doesn't. Then it requires multiple reloads, or at the worst, closing the tab, to get it to show up again. While the previous version had its faults, it was manageable compared to this.
怎么这么垃圾啊,f12插件都显示不出来,偶尔显示出来,偶尔显示不出来,搞毛啊?