-
-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vue Devtools not loading #909
Comments
Have you followed the upgrade guide for 2.0.0-rc.4 that has you switch to electron-devtools-installer? I think this may solve your problem. |
well, unfortinately, i faced the same problem. It is still there |
@nklayman well that's why the line |
I have the same issue. Starting yesterday the Vue devtools just disappeared 🥶 I've updated vue-cli-plugin-electron-builder from 1.4.6 to v2.0.0-rc.4 and followed the instructions about installExtension - nothing changed. After I've updated Electron to 9.0.0 I started getting the same warnings. The extension still not works. Tried that solution without any success: Since until yesterday seems that everything was working fine, maybe the reason is in Vue devtools update or something like that? |
@DKhalil my bad, for some reason I thought I saw the old method there 🤦. It works fine for me, and I don't have any suggestions to fix it. Try using the electron-quick-start repo and adding electron-devtools-installer, then installing vue devtools. If it doesn't work there, then it is an issue with vue devtools or electron-devtools-installer. |
@nklayman what does your package.json look like? Maybe there's a version mismatch happening.
|
My |
@nklayman @ton77v @OverlyDramatic One more piece to this whole thing: I'm on Windows 10, are any of you on Linux? |
I use Ubuntu, but I can test on windows soon. |
I'm @ Windows10 |
Windows 10 1909 there. i find that devtools would fail to load every day when i npm run electron:serve for the first time. But when i close and reopen it, i can find Devtools there. :) here is my package.json. by the way i used typescript. {
"name": "balabala",
"version": "0.1.0",
"private": true,
"scripts": {
"serve": "vue-cli-service serve",
"build": "vue-cli-service build",
"test:unit": "vue-cli-service test:unit",
"lint": "vue-cli-service lint",
"electron:build": "vue-cli-service electron:build",
"electron:serve": "vue-cli-service electron:serve",
"postinstall": "electron-builder install-app-deps",
"postuninstall": "electron-builder install-app-deps"
},
"main": "background.js",
"dependencies": {
"@types/pouchdb": "^6.4.0",
"core-js": "^3.6.5",
"jsmediatags": "^3.9.3",
"pouchdb": "^7.2.1",
"vue": "^2.6.11",
"vue-class-component": "^7.2.3",
"vue-property-decorator": "^8.4.2",
"vue-router": "^3.2.0",
"vuetify": "^2.2.11",
"vuex": "^3.4.0"
},
"devDependencies": {
"@types/jest": "^24.0.19",
"@typescript-eslint/eslint-plugin": "^2.33.0",
"@typescript-eslint/parser": "^2.33.0",
"@vue/cli-plugin-babel": "~4.4.0",
"@vue/cli-plugin-eslint": "~4.4.0",
"@vue/cli-plugin-router": "~4.4.0",
"@vue/cli-plugin-typescript": "~4.4.0",
"@vue/cli-plugin-unit-jest": "~4.4.0",
"@vue/cli-plugin-vuex": "~4.4.0",
"@vue/cli-service": "~4.4.0",
"@vue/eslint-config-prettier": "^6.0.0",
"@vue/eslint-config-typescript": "^5.0.2",
"@vue/test-utils": "^1.0.3",
"electron": "^9.0.0",
"electron-devtools-installer": "^3.1.1",
"eslint": "^6.7.2",
"eslint-plugin-prettier": "^3.1.3",
"eslint-plugin-vue": "^6.2.2",
"lint-staged": "^9.5.0",
"node-sass": "^4.12.0",
"prettier": "^1.19.1",
"sass": "^1.19.0",
"sass-loader": "^8.0.2",
"typescript": "~3.9.3",
"vue-cli-plugin-electron-builder": "~2.0.0-rc.4",
"vue-cli-plugin-vuetify": "~2.0.7",
"vue-template-compiler": "^2.6.11",
"vuetify-loader": "^1.3.0"
},
"gitHooks": {
"pre-commit": "lint-staged"
},
"lint-staged": {
"*.{js,jsx,vue,ts,tsx}": [
"vue-cli-service lint",
"git add"
]
}
}
|
This might be related to this issue? electron/electron#24011 Edit: Downgrading to electron@8.4.0 seems to fix it, so it's probably an electron@9 issue |
im going to check it out. thanks there 👍 |
Experiencing the same issue. I swear it was working yesterday and now it's just not showing up. |
Exactly the same happened with me few days ago. And the weird thing is that I had Electron 5 that time and did all the updates AFTER the problems appeared |
Can those of you with the issue please try this: #776 (comment) (adding |
Sadly mine already had the await. Just to clarify you mean like this right?
|
@Chappie74 The await code is for |
Oh I completely missed that with my hurried/frustrated reading. Worked like a charm. Thanks, bro. |
I've tried this before without any success, in my case using 'await' results in the application doesn't load at all. This is probably because I have 2 windows, one is "splash" to show during the load I've created the gist with the relevant code: Any ideas on how to implement "..wait" in my case? 🤔 thx |
I added await to the webpack server but I'm still getting the same issue as the OP. |
@nklayman yes, for me that fixes it with electron@9.1.1 ! Thanks |
I'm going to close this as the workaround I posted fixed it for @DKhalil and others. The @Stanzilla please open a new issue that follows the bug report template so that I can get more information and try and figure out why the fix didn't work for you. @ton77v you're issue doesn't seem to be related to devtools, rather just not being able to |
In my case, Vue Devtools works well, but the warning still exists. |
Thanks to @nklayman my problem is fixed now 👍 Although I can see the warning anyway anything works fine with the DevTools. In my case the solution is https://gist.github.com/ton77v/25108a7d7c0da7c98c7e45cbaabf76f5#gistcomment-3397339 |
I was experiencing this problem using the following setup:
When booting up the application using: update all instances of |
This solved it for me, Thanks!!!!!! |
Describe the bug
After the first initial run when the devtools are still being loaded, they're not available anymore.
When running
npm run electron:serve
I get this warning message:Which is most likely coming from this line:
await installExtension(VUEJS_DEVTOOLS)
package.json:
It seems possible to "fix" this by deleting the temporary build and forcing a rebuild.
The text was updated successfully, but these errors were encountered: