Closed niksy closed 1 month ago
Name | Link |
---|---|
Latest commit | 2e60f5396c9f0ddd0e42e1014a61e3b55536e98e |
Latest deploy log | https://app.netlify.com/sites/vue-devtools-docs/deploys/6707d9e857180a0008dada81 |
ideally, of course to find his name by meta router, or just the parent's folder but of course that would require resources
Great! Thanks 🙏
``` pnpm add https://pkg.pr.new/@vue/devtools-applet@628 ```
``` pnpm add https://pkg.pr.new/@vue/devtools-core@628 ```
``` pnpm add https://pkg.pr.new/@vue/devtools@628 ```
``` pnpm add https://pkg.pr.new/@vue/devtools-api@628 ```
``` pnpm add https://pkg.pr.new/@vue/devtools-kit@628 ```
``` pnpm add https://pkg.pr.new/vite-plugin-vue-devtools@628 ```
commit: 2e60f53
Similar to https://github.com/vuejs/devtools-v6/pull/1994
Sometimes developers have components nested inside directories and follow classic Node approach of naming them
/index.${extension}
, in this case/index.vue
. Devtools currently display every component as<Index>
unless you specify name. This PR will check for those components and use parent directory as component name.