Skip to content

DevTools extension #1644

New issue
New issue
Closed
Closed
DevTools extension#1644

Description

@wormen
wormen
opened on May 11, 2015

you have the documentation
https://github.com/atom/electron/blob/master/docs/tutorial/devtools-extension.md
It described that can use plug-ins from google chrome, made as described therein, and then get an error

Uncaught TypeError: Cannot read property 'getURL' of undefined", source: chrome-extension://extension-1//panes/assets/ember-inspector.js (1)

code, a request of this type

chrome.extension.getURL("/panes/ember_debug.js")

so that the error is not exactly in the plugin, as it is normal in the google chrome working

Activity

  1. sbruchmann commented on May 13, 2015

    @sbruchmann
    sbruchmann
    on May 13, 2015

    Hello @wormen,

    citing docs you’ve linked:

    chrome.* APIs

    Some chrome extensions use chrome.* APIs for some features, there is some effort to implement those APIs in Electron to make them work, but we have only implemented few for now.

    So if the devtools extension is using APIs other than chrome.devtools.*, it is very likely to fail, but you can report those extensions in the issues tracker so we can add support for those APIs.

    These paragraphs should answer your original issue.

    Would you like to request that the team and/or the community implement chrome.extension.getURL?

  2. wormen commented on May 13, 2015

    @wormen
    wormen
    on May 13, 2015
    Author

    Yes, if you can, it would be a good idea to implement support Ember and React

  3. bruce commented on May 14, 2015

    @bruce
    bruce
    on May 14, 2015

    I'd also like to request this feature; we're building an Ember-based application that interacts with hardware on top of Electron, and this would be extremely useful for debugging during development.

  4. bobisjan commented on May 15, 2015

    @bobisjan
    bobisjan
    on May 15, 2015

    It would be great if Electron will support Ember Inspector.

    Except chrome.extension.getURL, chrome.extension.connect is also being used by inspector.

  5. anaisbetts commented on May 15, 2015

    @anaisbetts
    anaisbetts
    on May 15, 2015
    Contributor

    This is weird because according to the code, chrome.extension.getURL is already implemented (in fact, it's the only chrome.* API implemented)

  6. deepak1556 commented on May 16, 2015

    @deepak1556
    deepak1556
    on May 16, 2015
    Member

    @wormen did you load with absolute path ?

    >  require('remote').require('browser-window').addDevToolsExtension(require('path').join(__dirname, 'ember-inspector', 'dist_chrome'))
<- "Ember Inspector"

    But yeah we need to support content-scripts for react. ember and like extensions. can we track this under one issue #915

  7. wormen commented on May 16, 2015

    @wormen
    wormen
    on May 16, 2015
    Author

    @deepak1556 yes, I have an absolute path

  8. zcbenz commented on May 19, 2015

    @zcbenz
    zcbenz
    on May 19, 2015
    Contributor

    I'm merging this to #915.

  9. zcbenz
    closed this as completedon May 19, 2015
  10. claude
    added 2 commits that reference this issue on Nov 2, 2026

    chore: update patches

    962daef

    8642609: [M156] Defer entry removal until database scan iterator is d…

    3acb81d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions