Help request - Nearly-empty screen after installation

[eddow]

I just wanted to try as the screenshots looked nice, but I was unable to even see localy how DejaVue works I end up with a screen containing two titles and a slider bar with a button "Resume App" appearing some times

[iraklisg]

same issue here... In some pages the plugin does work, in some other simply not...

[james-brndwgn]

I also just downloaded this to try it out. Seeing the same thing. My console log is full of nodes, but the DejaVue tab is pretty much blank.

[hikerpig]

Same issue here, using Chrome 59.0.3071.115

[sschwartz0]

Are any of you using this on public repos that we can checkout to debug? My initial reaction is that this is happening because your app is updating pretty quickly before initial load. Can you try loading the page and then opening up dejavue?

[eddow]

Well, I re-installed to test it on one of my live repository, there is already something appearing but I am not sure this is the whole story and the displayed elements seem erratic

Rectification : after reloading, the screen is again completely blank with only the timeline.

test url: https://rawgit.com/eddow/v-semantic/master/test/index.html#/form

[nshCore]

Same with me doesn't work wither just shows a blank page, tried removing and reinstalling, same thing happens.

Mac OSX 10.12.5 Chrome Version 61.0.3163.100 (Official Build) (64-bit)

installed packages

npm list --depth=0

quasar-app@0.0.1 /srv/clients/{someClient}/app ├── autoprefixer@6.7.7 ├── axios@0.16.2 ├── babel-core@6.26.0 ├── babel-eslint@7.2.3 ├── babel-loader@7.1.2 ├── babel-plugin-transform-runtime@6.23.0 ├── babel-preset-es2015@6.24.1 ├── babel-preset-stage-2@6.24.1 ├── babel-runtime@6.26.0 ├── colors@1.1.2 ├── connect-history-api-fallback@1.4.0 ├── css-loader@0.28.7 ├── es6-promise@4.1.1 ├── eslint@4.9.0 ├── eslint-config-standard@10.2.1 ├── eslint-friendly-formatter@3.0.0 ├── eslint-loader@1.9.0 ├── eslint-plugin-html@3.2.2 ├── eslint-plugin-import@2.8.0 ├── eslint-plugin-node@5.2.0 ├── eslint-plugin-promise@3.6.0 ├── eslint-plugin-standard@3.0.1 ├── eventsource-polyfill@0.9.6 ├── express@4.16.2 ├── extract-text-webpack-plugin@3.0.1 ├── file-loader@0.11.2 ├── friendly-errors-webpack-plugin@1.6.1 ├── glob@7.1.2 ├── html-webpack-plugin@2.30.1 ├── http-proxy-middleware@0.17.4 ├── json-loader@0.5.7 ├── opn@5.1.0 ├── optimize-css-assets-webpack-plugin@3.2.0 ├── postcss-loader@1.3.3 ├── progress-bar-webpack-plugin@1.10.0 ├── purify-css@1.2.6 ├── quasar-extras@0.0.8 ├── quasar-framework@0.14.6 ├── shelljs@0.7.8 ├── stylus@0.54.5 ├── stylus-loader@3.0.1 ├── url-loader@0.5.9 ├── vue@2.5.2 ├── vue-authenticate@1.3.1 ├── vue-avatar@2.0.0 ├── vue-axios@2.0.2 ├── vue-loader@13.3.0 ├── vue-places@1.1.0 ├── vue-router@3.0.1 ├── vue-style-loader@3.0.3 ├── vue-template-compiler@2.5.2 ├── vuelidate@0.6.1 ├── vuex@3.0.0 ├── vuex-i18n@1.7.0 ├── vuex-rest-api@2.4.1 ├── vuex-router-sync@5.0.0 ├── webpack@3.8.1 ├── webpack-dev-middleware@1.12.0 ├── webpack-hot-middleware@2.20.0 └── webpack-merge@4.1.0

[hosein2398]

Same issue here, not working at all on Chrome 64

[HopeEternal]

@sschwartz0 @kimhjona @madebymtr @nihgwu Any chance you may continue support for this app in future? I LOVE your idea for this Vue component visualizer!

I've also found that even today. your extension still works on Vue version 2.6.11 apps even with VueX and Router installed. Unfortunately, as others have stated, the behavior is erratic and in 75% of cases, I get the same issue with a blank window and no Dom Tree Nodes showing in the DejaVue extension panel on the right. It would be incredibly useful for debugging some very large apps that I've been working with, so I'm wondering if I need to roll up my sleeves and write my script to do this, or if you may consider updating this extension in the future. Thank you!

[sschwartz0]

@HopeEternal this project was actually our capstone at a coding bootcamp we all did together. Surprised to see it still works even 25% of the time! It's not a sophisticated solution but that's probably why it still kind of works.

Unless @kimhjona or @madebymtr say otherwise there are no plans to fix this up.

[HopeEternal]

@sschwartz0 It's an amazing idea and incredibly useful! I'm doing a presentation at work on it today since I spent yesterday looking for Component Hierarchy Visualization Tools for Vue, and DejaVue seems to be the only one out there. Fingers crossed that one of the other creators is interested in reviving it! Thanks for your prompt response. :)