I've been using Vue devtools extension with Electron and whenever I activate and use Vue devtools, all the errors occurred from it gets printed out to the Electron's main process console like this.
It's so frustrating because It's hard to find any useful information printed out from my application in middle of these thousands of errors.
I know why the error occurs. It's because Vue devtools is trying to access the chrome.tabs.captureVisibleTab() function which isn't available on Electron but I don't really care about the errors occurring from Vue devtools here. I just need to stop Electron from printing these errors out. Looked through all of the devtools related documentation but found nothing on this.
Related
I'm using phantomjs to scrape a page that uses vega-lite charts, however I keep getting this error whenever my code calls vegaEmbed:
ReferenceError: Can't find variable: vegaEmbed
I'm guessing this has something to do with phantomjs not supporting ES6. Can anyone confirm?
Sometimes I add a new variable to the Vue data() and get a ReferenceError (like "ReferenceError: windowHeight is not defined"), then when I check the error in the Firefox's debugger, I see that Vue in debugger is the old code not the one I have in my IDE. But when I try the exact same thing in Private Browsing I can see the code being exactly the same as my IDE.
Is this some kind of caching problem? Or is it related to my IDE which is VSCode. And how can I solve it?
I was expecting to see the same code as in my IDE, but during debug I see the old one.
I cannot manage to get the Vue DevTools running with my iOS Nativescript Project. I followed exactly the instruction on https://nativescript-vue.org/en/docs/getting-started/vue-devtools/ but the Nativescript App does not connect to vue-devtools.
I'm working on a Mac having latest Nativescript 8.1.3 installed, nativescript-vue-devtools is version 1.5.1.
One thing I notice is the error message ReferenceError: SocketManager is not defined as soon as I put Vue.use(VueDevtools) into the code. This error message always appears, I tried several Simulators with different iOS version, I also tried a physical device. I also tried with a "fresh" blank Vue project, leaving completely unchanged but just adding the Vue Devtools, same error.
Anyone out there who managed to get this working?
Thank you for your help.
I am trying to access my VueJS application running on my node server on IE11 by accessing the URL http://localhost:8080. However I cant access the same as only a blank screen appears. I have babel polyfill installed and imported in my main file and have babel presets already setup in babelrc file.
My app is currently running and is accessible on Chrome but not on IE11.
I don't get a single error message in console and have no clue what could be going wrong. Has anyone ever faced this?
You need to use polyfills. IE11 does not support ES2015, it needs to be transiled by babel. There seem to be various ways of doing this.
Please check this guide: jacklyons.me/how-to-fix-vuejs-not-working-in-ie11
or here: cli.vuejs.org/guide/browser-compatibility.html
I've just lost a frustrating amount of time trying to work out why npm run serve was hanging when attempting to run my vue js app. Eventually, I tracked it down to one error in a vue file I made, it took me a long time to work this out since the issue manifests itself in a way that the console window just hangs.
Is there some other way developers can get a more descriptive error list from vue js prior to attempting to run/build?
Personally, I find the most useful and essential tools to be (I use VS Code as "IDE")
Vetur: includes syntax-highlighting, snippets, linter (error checking), auto completition, etc.
Vue.js devtools (for chrome): Not sure about other browsers, but this is incredibly useful for chrome. Let's you see what's really going on with vue.js' components, the store, etc (screenshot from the chrome store page).
Hope this helps!