extreload/extension, branch master Reload Chrome extensions from the command line Remove web extension and native messaging host 2021-02-27T17:54:54+00:00 Teddy Wing 2021-02-27T17:54:54+00:00 cbd9d28467f03569f464cbd0628fed73e4a6cd32 This code is superseded by the Common Lisp project that communicates via the DevTools Protocol. The `chrome.management` API's `setEnabled()` function just allowed me to turn extensions off and on. It didn't reload the extensions. The DevTools Protocol allows us to execute JavaScript in the context of an extension's background page. This allows us to run `chrome.runtime.reload()` in an extension's context, properly reloading the extension. 
This code is superseded by the Common Lisp project that communicates via
the DevTools Protocol.

The `chrome.management` API's `setEnabled()` function just allowed me to
turn extensions off and on. It didn't reload the extensions.

The DevTools Protocol allows us to execute JavaScript in the context of
an extension's background page. This allows us to run
`chrome.runtime.reload()` in an extension's context, properly reloading
the extension.
Set up Native Messaging and reload extensions 2021-01-17T17:34:35+00:00 Teddy Wing 2021-01-17T17:34:35+00:00 bce9f260c66c7b4399d85eddc38c8d19dfa0cf43 Get the extension IDs from the Native Messaging host and reload the specified extensions. Also reload the current tab. Turns out this doesn't work the way I expected. It does disable and re-enable the extension, but it doesn't reload the extension as with `chrome.runtime.reload()`. This means the specified extension isn't reloaded with the latest code changes. Unfortunately, it looks like there's no API to do what I want, and unless there's some magic in the `chrome.debugger` API I'll have to give up on this project. 
Get the extension IDs from the Native Messaging host and reload the
specified extensions. Also reload the current tab.

Turns out this doesn't work the way I expected. It does disable and
re-enable the extension, but it doesn't reload the extension as with
`chrome.runtime.reload()`. This means the specified extension isn't
reloaded with the latest code changes.

Unfortunately, it looks like there's no API to do what I want, and
unless there's some magic in the `chrome.debugger` API I'll have to give
up on this project.
manifest.json: Add public key 2021-01-17T15:09:02+00:00 Teddy Wing 2021-01-17T15:07:10+00:00 05544f7b31667c3a74d3ab254d53475e0f201b0d Allows us to get a permanent extension ID that we can refer to for Native Messaging (ID: pacpdcpgfbpkdpmhfaljffnfbdanmblh). Generated the key with: $ openssl rsa -in key.pem -pubout -outform DER 2>/dev/null | openssl base64 -A && echo Using the explanation provided by Rob W (https://stackoverflow.com/users/938089/rob-w) on Stack Overflow: https://stackoverflow.com/questions/23873623/obtaining-chrome-extension-id-for-development/23877974#23877974 
Allows us to get a permanent extension ID that we can refer to for
Native Messaging (ID: pacpdcpgfbpkdpmhfaljffnfbdanmblh).

Generated the key with:

    $ openssl rsa -in key.pem -pubout -outform DER 2>/dev/null | openssl base64 -A && echo

Using the explanation provided by Rob W
(https://stackoverflow.com/users/938089/rob-w) on Stack Overflow:
https://stackoverflow.com/questions/23873623/obtaining-chrome-extension-id-for-development/23877974#23877974
Add manifest.json 2021-01-17T14:46:28+00:00 Teddy Wing 2021-01-17T14:46:28+00:00 2a5a08d91b800b21b207d282dadb47d4266ddcac