Last 12 weeks · 0 commits
3 of 6 standards met
Vue devtools version 6.6.4 Link to minimal reproduction 没有 Steps to reproduce & screenshots Extension server error: Operation failed: Permission denied 在Edge 142版本存在无法打开调试vue-devtool , 在141则可以正常打开,而且我试过了v5也是不可以,降低版本则可以 What is expected? 正常打开vue调试工具 What is actually happening? 无法打开调试工具 System Info Any additional comments? 没有
Vue devtools version 6.6.4 Link to minimal reproduction https://github.com/vuejs/devtools-v6.git Steps to reproduce & screenshots the issue process: 1. Package the project and upload it to the Chrome extension. When loading the dev Vue page, dev tools encountered an error: Uncaught (in promise) TypeError: object null is not iterable (cannot read property Symbol(Symbol.iterator)),This error prevents vue devtools from running properly 2. After troubleshooting, it was found that this code appears in the icon.ts file: const [, content] = /(.)/.exec(result),Is this question because:/The result of (. )/. exec (result) is null,null cannot be deconstructed. 3.Trying to print icons (keys) resulted in a base64 string instead of the original SVG string 4.That's why null appears when deconstructing, because the result of icons (keys) is a base64 string, not the original string like this\...\ 5.The path where the problem code appears is:/packages/app-frontend/src/features/ui/components/icons.ts What is expected? The expected outcome was that the plugin was running normally, but TypeError: object null is not iterable (cannot read property Symbol(Symbol.iterator)) error caused vue devtools to not run properly What is actually happening? vue devtools to not run properly System Info Any additional comments? The path where the problem code appears is:/packages/app-frontend/src/features/ui/components/icons.ts**
Version 6.0.0-beta.15 Browser and OS info Chrome 91, Any OS Steps to reproduce Reproduction repo: https://github.com/sheremet-va/vue-devtools-bug install packages () run open open vue devtools window inside chrome devtools you can see that everything is working fine refresh the page (F5 or Cmd R) devtools shows components, but isn't interactable What is expected? interactable devtools What is actually happening? devtools showing cached components Our application loads user data before mounting showing progress bar. There are a lot of ways of handling it, and we like our approach, but we also want to use devtools!
Version 5.3.3 Browser and OS info Firefox 76 / Mint 19.3 Steps to reproduce What is expected? Display the value of a property in inspector when it is a primitive wrapper. What is actually happening? Displaying the type of a property Perhaps checking the type of the variable with instanceof might solve the problem
Vue devtools version 6.4.5 Link to minimal reproduction n/a I am able to reproduce the error with a minimal app: Steps to reproduce & screenshots 1. Open Dev Tools on a website with Vue application 2. Go to the "Vue" tab in the dev tools 3. Close Dev Tools Monitor RAM usage to see the memory leak: !grafik What is expected? Memory stays constant. What is actually happening? Memory usage increases and within a few seconds all memory is used. System Info Any additional comments? How can I debug this issue to give you the required information? I am unable to re-open the Dev Tools after closing them for the first time, so I cannot export a memory dump or a profiler recording. I cannot leave the Dev Tools open since the bug only occurs when closing them.
Repository: vuejs/devtools-v6. Description: ⚙️ Browser devtools extension for debugging Vue.js applications. Stars: 24719, Forks: 4133. Primary language: TypeScript. Languages: TypeScript (45.1%), Vue (38.2%), JavaScript (14.6%), HTML (1.2%), Stylus (0.6%). License: MIT. Homepage: https://devtools-v6.vuejs.org/ Latest release: v6.6.4 (1y ago). Open PRs: 37, open issues: 476. Last activity: 1y ago. Community health: 50%. Top contributors: Akryum, yyx990803, posva, bartlomieju, Azurewarth0920, zigomir, konpeki622, markussorg, anteriovieira, michalsnik and others.