-
Notifications
You must be signed in to change notification settings - Fork 15k
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
Devtron will not load in 9.0.0 #23676
Comments
Unfortunately, due to bugs in Electron 9, we can't use devtron (electron/electron#23676). We could at least get Ember Inspector to load (using the workaround for electron/electron#23656), but hopefully Electron will turn around a quick fix at least for that second issue so we don't have to add a temporary workaround to the blueprint-generated code...
Unfortunately, due to bugs in Electron 9, we can't use devtron (electron/electron#23676). We could at least get Ember Inspector to load (using the workaround for electron/electron#23656), but hopefully Electron will turn around a quick fix at least for that second issue so we don't have to add a temporary workaround to the blueprint-generated code...
Unfortunately, due to bugs in Electron 9, we can't use devtron (electron/electron#23676). We could at least get Ember Inspector to load (using the workaround for electron/electron#23656), but hopefully Electron will turn around a quick fix at least for that second issue so we don't have to add a temporary workaround to the blueprint-generated code...
Please report to https://github.com/electron-userland/devtron/issues |
@miniak any clue on what changed on the Electron/Chromium side that might have started causing this failure in 9.x to tell the Devtron folks? |
@miniak devtron repo is pretty much dead, no commits since 2018. so imo it's Electron team who should fix the issue since devtron worked fine before E9 |
If https://www.electronjs.org/devtron is going to stay live then I think that Devtron issues should not be ignored by the Electron team, especially since this issue persists. If it's only usable on versions of Electron the team no longer supports, then I think that page should be removed, or at least make obvious note of that. It's currently listed as, "Official DevTools extension." but that seems not to be the case. Devtron was (is) a crucial tool and to lose it just when Electron starts really moving everyone towards IPC communications is a major loss for developers. |
Preflight Checklist
Issue Details
Expected Behavior
Running
require('devtron').install()
from the renderer process console or main process successfully installs the devtron extensionActual Behavior
If run from the main process it fails with:
and similar if it is run from the renderer process' console
To Reproduce
Run
yarn init -y && yarn add --dev electron@9 devtron
. Put this inindex.js
:Run
yarn electron .
and observe the error in the console. Open the devtools console in the browser window and runrequire('devtron').install()
-- same result.The text was updated successfully, but these errors were encountered: